On Fri, Dec 2, 2011 at 6:25 PM, Daniel Farina <dan...@heroku.com> wrote: > Here's a protocol: have pg_start_backup() write a file that just means > "backing up". Restarts are OK, because that's all it means, it has no > meaning to a recovery/restoration process. > > When one wishes to restore, one must touch a file -- not unlike the > trigger file in recovery.conf (some have argued in the past this > *should* be recovery.conf, except perhaps for its tendency to be moved > to recovery.done) to have that behavior occur.
It certainly doesn't seem to me that you need TWO files. If you create a file on the master, then you just need to remove it from the backup. But I think the use of such a new protocol should be optional; it's easy to provide backward-compatibility here. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
