| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
| Date: | 2009-02-19 07:35:14 |
| Message-ID: | 499D0BB2.50604@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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.
> Given the shape of the patch, the likely fix is to bump
> NUM_AUXILIARY_PROCS by one.
Not sure what you mean by the shape of the patch, but agreed.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-02-19 08:02:32 | pgsql: Increase NUM_AUXILIARY_PROCS, now that the startup process can |
| Previous Message | Tom Lane | 2009-02-18 23:33:12 | Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2009-02-19 07:58:19 | Re: WIP: hooking parser |
| Previous Message | Jacky Leng | 2009-02-19 05:24:31 | Doubts about EvalPlanQual |