| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Need solution for weekly database "snapshot" |
| Date: | 2013-04-22 16:14:45 |
| Message-ID: | 20130422161445.GG3958@hermes.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Apr 22, 2013 at 11:58:58AM -0400, Moshe Jacobson 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.
>
> The problem is that backing up and restoring the database every week is a
> very costly operation that can take many hours. It brings the system to its
> knees.
Setup a slave.
Sunday at noon let main DB reach a consistent state, "stop"
it, let slave catch up, detach slave Sunday at noon, restart
main, backup from slave, re-attach slave.
Similar things can be done with things like Btrfs at the FS level.
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Moshe Jacobson | 2013-04-22 17:05:30 | Re: Need solution for weekly database "snapshot" |
| Previous Message | Moshe Jacobson | 2013-04-22 15:58:58 | Need solution for weekly database "snapshot" |