| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
| Date: | 2009-02-18 22:16:26 |
| Message-ID: | 1234995386.3973.156.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, 2009-02-18 at 21:28 +0000, Simon Riggs wrote:
> On Wed, 2009-02-18 at 15:43 -0500, Tom Lane wrote:
> > heikki(at)postgresql(dot)org (Heikki Linnakangas) writes:
> > > Log Message:
> > > -----------
> > > Start background writer during archive recovery.
> >
> > Might that have anything to do with this?
> >
> > http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=dungbeetle&dt=2009-02-18%2019:44:01
>
> Hmmm, looks very probable. But not anything that jumps out quickly at
> me. Will continue to check.
Finger points that way, but still can't see any specific reason for
that.
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.
Given the shape of the patch, the likely fix is to bump
NUM_AUXILIARY_PROCS by one.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Bmomjian | 2009-02-18 22:29:20 | pg-migrator - src: Remove duration report at end, clean up API. |
| Previous Message | Simon Riggs | 2009-02-18 21:28:55 | Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-02-18 22:22:05 | Re: The science of optimization in practical terms? |
| Previous Message | Simon Riggs | 2009-02-18 21:28:55 | Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |