Re: crash-safe visibility map, take three - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: crash-safe visibility map, take three
Date
Msg-id 4CF5337E.8000505@enterprisedb.com
Whole thread Raw
In response to Re: crash-safe visibility map, take three  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: crash-safe visibility map, take three
List pgsql-hackers
On 30.11.2010 19:22, Tom Lane wrote:
> But having said that, I wonder whether we need a full-page image for
> a WAL-logged action that is known to involve only setting a single bit
> and updating LSN.  Would omitting the FPI be any more risky than what
> happens now (ie, the page does get written back to disk at some point,
> without any image from which it can be rewritten if the write fails...)

You have to write a full-page image if you update the LSN, because 
otherwise the next update that comes along will not write a full page image.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: crash-safe visibility map, take three
Next
From: Robert Haas
Date:
Subject: Re: crash-safe visibility map, take three