Re: [HACKERS] Incrementally Updated Backup - Mailing list pgsql-patches

From Tom Lane
Subject Re: [HACKERS] Incrementally Updated Backup
Date
Msg-id 18412.1158783990@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Incrementally Updated Backup  ("Jim C. Nasby" <jim@nasby.net>)
Responses Re: [HACKERS] Incrementally Updated Backup
List pgsql-patches
"Jim C. Nasby" <jim@nasby.net> writes:
> 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.

Why wouldn't you implement that by putting N postmasters onto the backup
server?  It'd be far more efficient than the proposed patch, which by
aborting at random points is essentially guaranteeing a whole lot of
useless re-replay of WAL whenever you restart it.

            regards, tom lane

pgsql-patches by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: [HACKERS] Incrementally Updated Backup
Next
From: "Jim C. Nasby"
Date:
Subject: Re: [HACKERS] Incrementally Updated Backup