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

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Reset btpo.xact following recovery of btree delete page.
Date
Msg-id 29112.1269002483@sss.pgh.pa.us
Whole thread Raw
Responses Re: [COMMITTERS] pgsql: Reset btpo.xact following recovery of btree delete page.
List pgsql-hackers
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.

The correct thing to do when committing such a change is to change the
WAL-file magic number XLOG_PAGE_MAGIC.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUG] SECURITY DEFINER on call handler makes daemon crash
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL