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

From Simon Riggs
Subject Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque
Date
Msg-id CA+U5nMKsPed8+YeQSZCtYrbM-vuMwkGEPUE1Lu23Zy0rrHUjFw@mail.gmail.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque
List pgsql-hackers
On 1 June 2012 14:29, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Surely that commit is useless.  Fsync requests go into a queue in shared
> memory, which had better have been set up by the postmaster.  There is
> no requirement that the receiving process exist before somebody can put
> a request into the queue.  If the queue overflows, the requestor has to
> take care of the fsync itself, but that is independent of whether the
> checkpointer is running yet.

The problem I saw was about fsync queue message overflow, not actually
missing fsyncs, so perhaps I worded the commit message poorly.

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


pgsql-hackers by date:

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