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

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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-25 22:18:37
Message-ID: 4A43F7BD.8080806@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Heikki Linnakangas wrote:
> Tom Lane wrote:
>>  I wouldn't consider that a
>> good idea from a reliability standpoint either --- the more writes to
>> pg_control, the more risk of fatal corruption of that file.
> 
> We certainly update it an order of magnitude more often than before, but
> I don't think that's an issue. We're talking about archive recovery
> here. It's not like in normal operation where a corrupt pg_control file
> means that you lose your data. It will stop the server from starting up,
> but there's many other files that can be corrupt in a way that causes
> recovery to fail or stop too early.

If you still find the frequent pg_control updates unacceptable, we could
always move minRecoveryPoint to a file of its own..

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

In response to

pgsql-bugs by date

Next:From: Simon RiggsDate: 2009-06-25 22:20:01
Subject: Re: BUG #4879: bgwriter fails to fsync the file in recoverymode
Previous:From: Heikki LinnakangasDate: 2009-06-25 22:14:03
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