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-25 19:02:03
Message-ID: 1245956523.4038.193.camel@ebony.2ndQuadrant (view raw or flat)
Thread:
Lists: pgsql-bugs
On Thu, 2009-06-25 at 14:46 -0400, Tom Lane wrote:

> On the other point: are we going to eliminate mdunlink's isRedo
> parameter?  Maybe the better thing is to have its callers pass the value
> of InArchiveRecovery?

We have one caller that is using a parameter incorrectly. It seems we
should correct the caller rather than change the API and potentially
effect all callers.

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


In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-06-25 19:03:22
Subject: Re: BUG #4879: bgwriter fails to fsync the file in recovery mode
Previous:From: Heikki LinnakangasDate: 2009-06-25 18:59:56
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