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

From Simon Riggs
Subject Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque
Date
Msg-id CA+U5nMJenRvgd-u_GO9cU_XivRQaB9qZy2Eoh9zn8OdZOiHn9A@mail.gmail.com
Whole thread Raw
Responses Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 1 June 2012 08:55, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> On 01.06.2012 10:28, Simon Riggs wrote:
>>
>> Checkpointer starts before bgwriter to avoid missing fsync requests.
>> Noted while testing Hot Standby startup.
>
>
> The processes are just forked and it will take some time for them to
> initialize. Isn't there still a race condition, where the bgwriter starts up
> first, and you still miss fsync requests?

Possibly...

How do we handle that same situation if the check pointer crashes? And
if normal backends can't send? We don't seem that tense about that
either.

How hard do we need to try to avoid this potential hole? I'm not sure,
so opinions please.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Create collation incorrect error code
Next
From: Sergey Koposov
Date:
Subject: Re: slow dropping of tables, DropRelFileNodeBuffers, tas