| 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-19 16:20:22 |
| Message-ID: | 499D86C6.4010905@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> Simon Riggs wrote:
>>> More likely to be an uncommon race condition, rather than a error
>>> specific to dungbeetle. If startup process death is slow, this could
>>> happen, though hasn't occurred in other tests.
>
>> True, the startup process can live for a short while concurrently with
>> bgwriter, walwriter and autovacuum launcher, before it exits.
>
> Maybe the postmaster should wait for startup process exit before
> deciding to open for business, instead of just a signal.
Not a bad idea. Although, there's nothing wrong with the current way
either. The startup process does a proc_exit(0) right after sending the
signal ATM, so there's no real work left at that point.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-02-19 16:22:53 | Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
| Previous Message | User Fxjr | 2009-02-19 15:20:42 | npgsql - Npgsql2: [#1010543] Parameter value 'Int32.MinValue' throw |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-02-19 16:22:53 | Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
| Previous Message | Heikki Linnakangas | 2009-02-19 16:06:35 | Re: Doubts about EvalPlanQual |