Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery.
Date
Msg-id 1234995386.3973.156.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Start background writer during archive recovery.  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery.
Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery.
List 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@postgresql.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.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [COMMITTERS] pgsql: Start background writer during archive recovery.
Next
From: Simon Riggs
Date:
Subject: Re: The science of optimization in practical terms?