On Sat, Nov 29, 2008 at 12:40 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Fri, 2008-11-28 at 19:53 +0900, Fujii Masao wrote:
>> On Fri, Nov 28, 2008 at 6:56 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> > Hi,
>> > The immediate shutdown (pg_ctl -m i stop) might not be able to
>> > kill the startup process during archive recovery. It's because
>> > the startup process calls system() which ignores SIGQUIT for
>> > executing the restore_command. So, only the startup process
>> > might survive the immediate shutdown and continue redoing up
>> > to the end. Is this desirable behavior? This sounds odd for me.
>> In RestoreArchivedFile(), there is the following code as the safeguard
>> against the termination of restore_command by signal. But the
>> safeguard might not work if restore_command defines its own signal
>> handler for SIGQUIT like pg_standby.
>> > signaled = WIFSIGNALED(rc) || WEXITSTATUS(rc) > 125;
>> > ereport(signaled ? FATAL : DEBUG2,
>> > (errmsg("could not restore file \"%s\" from archive: return code %d",
>> > xlogfname, rc)));
> Agree there is an existing problem.
> Suggest we fix it after the main patches are committed.
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Andrew Gierth||Date: 2008-11-29 03:07:49|
|Subject: BUG #4553: HOLD cursors not materializing results fully|
|Previous:||From: Peter Eisentraut||Date: 2008-11-28 23:28:47|
|Subject: Re: HEAD build failure on win32 mingw|