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: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(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-30 15:48:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On Fri, 2009-06-26 at 16:48 -0400, Tom Lane wrote:
>> * I find the RecoveryInProgress test in XLogNeedsFlush rather dubious.
>> Why is it okay to disable that?  For at least one of the two callers
>> (SetHintBits) it seems like the safe answer is "true" not "false".
>> This doesn't matter too much yet but it will for hot standby.

> IIUC you think it is safest to *not* write hint bits during Hot Standby?

Well, the point I was trying to make is that if you want the code to do
nothing then hot-wiring it to return "false" all the time during hot
standby doesn't accomplish that.  I think it probably is safe to update
hint bits during HS, but we need to think through the timing relative to
WAL processing and make sure that we don't set them too early.

Maybe that analysis has actually been done already, but there's no
evidence of it in the code or comments.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-06-30 16:54:43
Subject: Re: BUG #4894: [patch] documentation bug on 'include' directive
Previous:From: Alvaro HerreraDate: 2009-06-30 15:42:48
Subject: Re: BUG #4892: postmaster died and didn't restart

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