Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery.
От | Simon Riggs |
---|---|
Тема | Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
Дата | |
Msg-id | 1234995386.3973.156.camel@ebony.2ndQuadrant обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Start background writer during archive recovery. (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery.
Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
Список | 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 по дате отправления: