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: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-25 16:22:47
Message-ID: 1245946967.4038.160.camel@ebony.2ndQuadrant (view raw or flat)
Thread:
Lists: pgsql-bugs
On Thu, 2009-06-25 at 18:57 +0300, Heikki Linnakangas wrote:

> I came up with the attached patch, which includes Simon's patch to
> have all fsync requests forwarded to bgwriter during archive recovery.
> To fix the startup checkpoint issue, startup process requests a forced
> restartpoint, which will flush any fsync requests bgwriter has
> accumulated, before doing the actual checkpoint in the startup
> process.

That looks fine.

> This is completely untested still, but does anyone immediately see any
> more problems?

Nothing seen.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support


In response to

pgsql-bugs by date

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