Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque
Date
Msg-id 24914.1338561181@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On 1 June 2012 14:59, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Ah. �Well, as long as the overflowed fsyncs do get handled on the
>> requesting side, I see no bug here. �No objection to changing the order
>> in which we launch the processes, but as Heikki says, it's not clear
>> that that is really going to make much difference.

> If I see those messages again, I guess you'll be right.

> If that happens I suggest just adding a short wait at bgwriter startup.

Why?  Surely we are not that concerned about performance during the
startup transient.  Also, it is very easy to imagine that adding a delay
would make startup performance worse not better anyway.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque
Next
From: Florian Pflug
Date:
Subject: Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile