Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery.
Date
Msg-id 499E8C1E.8050602@enterprisedb.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery.  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Tom Lane wrote:
> Couldn't you get rid of PMSIGNAL_RECOVERY_COMPLETED altogether?  If the
> startup process exits with code 0, recovery is complete, else there
> was trouble.  I find this SetPostmasterSignal bit quite ugly anyway.

Right now, the startup process exits with code 0 also when it's told to 
exit with SIGTERM, ie. fast shutdown request, and the recovery-completed 
signal is used to differentiate those cases. But yeah, we can use 
another exit code for that. I'll look into that approach.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_restore --multi-thread
Next
From: Heikki Linnakangas
Date:
Subject: Re: GIN fast insert