Re: [COMMITTERS] pgsql: Reset btpo.xact following recovery of btree delete page. - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [COMMITTERS] pgsql: Reset btpo.xact following recovery of btree delete page.
Date
Msg-id 1269012749.3556.278.camel@ebony
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Reset btpo.xact following recovery of btree delete page.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 2010-03-19 at 08:41 -0400, Tom Lane wrote:
> sriggs@postgresql.org (Simon Riggs) writes:
> > Log Message:
> > -----------
> > Reset btpo.xact following recovery of btree delete page. Add btpo_xact
> > field into WAL record and reset it from there, rather than using
> > FrozenTransactionId which can lead to some corner case bugs.
> 
> Simon, you can't just whack WAL record contents around without a care.
> This commit breaks on-disk WAL compatibility and will result in possibly
> unrecoverable databases as soon as someone applies it; not to mention
> what will happen if an HS slave is not running the same code as its
> master.  This must be treated as an initdb-forcing, or at least
> pg_resetxlog-forcing, change.

OK, understood. 

> The correct thing to do when committing such a change is to change the
> WAL-file magic number XLOG_PAGE_MAGIC.

Will do

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Next
From: Robert Treat
Date:
Subject: Postgres officially accepted in to 2010 Google Summer of Code program