| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| 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 15:00:30 |
| Message-ID: | 7682.1235055630@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Fxjr | 2009-02-19 15:20:42 | npgsql - Npgsql2: [#1010543] Parameter value 'Int32.MinValue' throw |
| Previous Message | User Okbob | 2009-02-19 14:46:40 | orafce - orafce: include parser/parse_expr because exprType is defined |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-02-19 15:05:32 | Re: pg_restore new option -m |
| Previous Message | ohp | 2009-02-19 14:20:08 | Re: pg_restore new option -m |