From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | filippo <filippo2991(at)virgilio(dot)it> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: backup database by cloning itself |
Date: | 2007-02-15 17:55:11 |
Message-ID: | 20070215175511.GS4682@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
filippo wrote:
> On 14 Feb, 08:33, ron(dot)l(dot)john(dot)(dot)(dot)(at)cox(dot)net (Ron Johnson) wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > There's almost definitely a better way to do what you want to do.
> >
> > What benefit are you trying to obtain by creating 720 almost
> > identical databases per month?
>
> I only need the last 24, overwriting each day. In my case 8 are enough
> (8am to 24pm, one every 2 hours). The important thing is to be able to
> open each very simply (read only) without restore anything. Just tell
> my application (written be me), to point the basckup database instead
> of latest one.
I wonder if you could have a PITR warm standby instead, and every hour
stop it and backup that. This is very hand-wavy, you're expected to
fill in the details :-)
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2007-02-15 17:59:50 | Re: massive memory allocation until machine crashes |
Previous Message | Ted | 2007-02-15 17:54:14 | Re: backup database by cloning itself |