Skip site navigation (1) Skip section navigation (2)

Re: BUG #4879: bgwriter fails to fsync the file in recovery mode

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4879: bgwriter fails to fsync the file in recovery mode
Date: 2009-06-26 15:23:29
Message-ID: 6985.1246029809@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
I wrote:
> Hmm ... this doesn't really feel cleaner to me, although I'm not sure
> why not.

Oh, I thought of a more concrete point: InRecovery is inherently a
system-wide state, but XLogInsertAllowed is *not*.  While we write
the EOR checkpoint, we really want only the bgwriter to be authorized
to write WAL, but the scheme you propose would effectively authorize
all processes during that window.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: stalkerDate: 2009-06-26 15:37:55
Subject: BUG #4888: Removed brackets from Check Constraints expressions
Previous:From: Tom LaneDate: 2009-06-26 15:20:35
Subject: Re: BUG #4879: bgwriter fails to fsync the file in recovery mode

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group