Re: backup database by cloning itself - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: backup database by cloning itself
Date
Msg-id 20070215175511.GS4682@alvh.no-ip.org
Whole thread Raw
In response to Re: backup database by cloning itself  ("filippo" <filippo2991@virgilio.it>)
List pgsql-general
filippo wrote:
> On 14 Feb, 08:33, ron.l.john...@cox.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.

pgsql-general by date:

Previous
From: "Ted"
Date:
Subject: Re: backup database by cloning itself
Next
From: Richard Huxton
Date:
Subject: Re: massive memory allocation until machine crashes