On Fri, Dec 2, 2011 at 6:25 PM, Daniel Farina <daniel(at)heroku(dot)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
But I think the use of such a new protocol should be optional; it's
easy to provide backward-compatibility here.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2011-12-03 00:09:48|
|Subject: Re: Command Triggers|
|Previous:||From: Daniel Farina||Date: 2011-12-02 23:25:59|
|Subject: Re: backup_label during crash recovery: do we know how to