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:
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 14:35:44
Message-ID: 4A438B40.6020107@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Heikki Linnakangas wrote:
> Hmm, what happens when the startup process performs a write, and
> bgwriter is not running? Do the fsync requests queue up in the shmem
> queue until the end of recovery when bgwriter is launched? I guess I'll
> have to try it out...

Oh dear, doesn't look good. The startup process has a pendingOpsTable of
its own. bgwriter won't fsync() files that the startup process has
written itself. That needs to be fixed, or you can lose data when an
archive recovery crashes after a restartpoint.

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

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-06-25 14:49:09
Subject: Re: BUG #4879: bgwriter fails to fsync the file in recovery mode
Previous:From: Andreas WenkDate: 2009-06-25 14:27:21
Subject: BUG #4881: KDE 4.2 not running any more when installing one click installer from Enterprise DB

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