| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
| Date: | 2009-02-23 09:31:52 |
| Message-ID: | 49A26D08.1010405@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Heikki Linnakangas wrote:
> 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.
Committed that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-02-23 10:03:22 | pgsql: Add quotes to message |
| Previous Message | Heikki Linnakangas | 2009-02-23 09:28:51 | pgsql: Change the signaling of end-of-recovery. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-02-23 09:56:05 | Re: GIN fast insert |
| Previous Message | Boszormenyi Zoltan | 2009-02-23 08:14:34 | Re: 8.4 features presentation |