Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Incrementally Updated Backup

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org,Heikki Linnakangas <heikki(at)enterprisedb(dot)com>,pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Incrementally Updated Backup
Date: 2006-09-20 20:20:18
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
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(at)nasby(dot)net
EnterpriseDB      512.569.9461 (cell)

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2006-09-20 20:22:47
Subject: Re: Phantom Command ID
Previous:From: Jim C. NasbyDate: 2006-09-20 20:16:38
Subject: Re: Release notes

pgsql-patches by date

Next:From: Tom LaneDate: 2006-09-20 20:26:30
Subject: Re: [HACKERS] Incrementally Updated Backup
Previous:From: Bruce MomjianDate: 2006-09-20 19:56:01
Subject: Re: Dynamic linking on AIX

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group