| From: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Need solution for weekly database "snapshot" |
| Date: | 2013-04-22 17:05:30 |
| Message-ID: | CAJ4CxLmBQREidAV3WqvNtpt3wyn6oeOtttqFn_8GPx2=4t10=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Apr 22, 2013 at 12:14 PM, Karsten Hilbert
<Karsten(dot)Hilbert(at)gmx(dot)net>wrote:
> > We have a report in our system that is pulled many times each week, but
> > needs to be based off data from Sunday at noon. So every Sunday at noon,
> we
> > back up our main database and restore it into a new reporting snapshot
> > database.
>
> Setup a slave.
>
Not bad, but the transaction logs would fill up the file system. Besides,
it would not be worth it to set up a whole database cluster just for this
purpose.
Any alternatives?
--
Moshe Jacobson
Nead Werx, Inc. | Manager of Systems Engineering
2323 Cumberland Parkway, Suite 201 | Atlanta, GA 30339
moshe(at)neadwerx(dot)com | www.neadwerx.com
"Quality is not an act, it is a habit." -- Aristotle
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafał Pietrak | 2013-04-22 17:12:35 | Re: using text search |
| Previous Message | Karsten Hilbert | 2013-04-22 16:14:45 | Re: Need solution for weekly database "snapshot" |