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

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

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 recoverymode
Date: 2009-06-30 08:26:15
Message-ID: 1246350375.27964.43.camel@dn-x300-willij (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
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?

So we would treat all commits as async commits?

 Simon Riggs 
 PostgreSQL Training, Services and Support

In response to


pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2009-06-30 14:29:27
Subject: Re: BUG #4895: OneClickInstaller dont appreciatesClient_Encoding and also listen_addresses='*'
Previous:From: Uwe LiebehenzDate: 2009-06-30 07:20:11
Subject: BUG #4895: OneClickInstaller dont appreciates Client_Encoding and also listen_addresses='*'

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