On Fri, Feb 27, 2009 at 3:38 AM, Heikki Linnakangas
> I think the real problem here is that pg_standby traps SIGQUIT. The startup
> process doesn't receive the SIGQUIT because it's in system(), and pg_standby
> doesn't propagate it to the startup process either because it traps it.
Yes, you are right.
> I think we should simply remove the signal handler for SIGQUIT from
> I don't see how that helps, as we already have this in there:
> signaled = WIFSIGNALED(rc) || WEXITSTATUS(rc) > 125;
> ereport(signaled ? FATAL : DEBUG2,
> (errmsg("could not restore file \"%s\" from archive: return code %d",
> xlogfname, rc)));
> which means we already ereport(FATAL) if the restore command dies with SIGQUIT.
SIGQUIT should kill the process immediately, so I think that the startup
process as well as other auxiliary process should call exit(2) instead of
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2009-02-26 19:49:16|
|Subject: Re: Hot standby, recovery infra|
|Previous:||From: Dave Gudeman||Date: 2009-02-26 19:13:46|
|Subject: a proposal for an extendable deparser|