Re: [PATCHES] Incrementally Updated Backup - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: [PATCHES] Incrementally Updated Backup
Date
Msg-id 20060920202017.GY28987@nasby.net
Whole thread Raw
In response to Re: [PATCHES] Incrementally Updated Backup  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [PATCHES] Incrementally Updated Backup
List pgsql-hackers
On Wed, Sep 20, 2006 at 02:09:43PM +0100, Simon Riggs wrote:
> > But why in the world would you want to stop the slave to do it?  ISTM
> > we would want to arrange things so that you can copy the slave's files
> > while it continues replicating, just as with a standard base backup.
>
> You can do that, of course, but my thinking was that people would regard
> the technique as "unsupported", so I added a quick flag as a prototype.

An advantage to being able to stop the server is that you could have one
server processing backups for multiple PostgreSQL clusters by going
through them 1 (or more likely, 2, 4, etc) at a time, essentially
providing N+1 capability.
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Units in postgresql.conf.sample
Next
From: Tom Lane
Date:
Subject: Re: Phantom Command ID