From: | "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Immediate shutdown during recovery |
Date: | 2008-11-28 10:53:58 |
Message-ID: | 3f0b79eb0811280253o274d6d5bsa1b1654c3e8ca1ae@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
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)));
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2008-11-28 11:46:40 | Re: Distinct types |
Previous Message | Simon Riggs | 2008-11-28 10:01:02 | Re: Review: Hot standby |