| 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-20 10:55:26 |
| Message-ID: | 499E8C1E.8050602@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2009-02-20 11:53:33 | stackbuilder - wizard: Wordsmithing. |
| Previous Message | Peter Eisentraut | 2009-02-20 10:39:19 | pgsql: another small message tweak |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2009-02-20 11:58:41 | Re: GIN fast insert |
| Previous Message | Peter Eisentraut | 2009-02-20 10:48:47 | Re: WIP: hooking parser |