Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Josh Berkus wrote:
>> OK, so we need a way out of that cycle if the user is issuing
>> pg_stop_backup because they *already know* that archive_command is
>> failing. Right now, there's no way out other than a fast shutdown,
> Sure there is. Just kill the session, Ctrl-c or similar.
> pg_stop_backup() isn't actually doing anything at that point anymore;
> it's just waiting for the files to be archived before returning.
One objection to this is that it's not very clear to the user when
pg_stop_backup has finished with actual work and is just waiting for the
archiver, ie when is it safe to hit control-C? Maybe we should emit a
"backup done, waiting for archiver to complete" notice before entering
the sleep loop.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Erik Rijkers||Date: 2010-02-24 21:12:58|
|Subject: Re: testing cvs HEAD - HS/SR - xlog timeline 0
|Previous:||From: David E. Wheeler||Date: 2010-02-24 20:56:14|
|Subject: Re: pg_stop_backup does not complete |