Fix determination of broken LSN in OVERWRITTEN_CONTRECORD
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Fri, 26 Nov 2021 14:14:27 +0000 (11:14 -0300)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Fri, 26 Nov 2021 14:14:27 +0000 (11:14 -0300)
commitef41c3fd6c86d6fa504144996b339704347322c9
tree128af2b99ed7dd712dcea0ca6d47b1e2a42a8233
parent04875ae92f14c0b23438e5316d92f82518bb068a
Fix determination of broken LSN in OVERWRITTEN_CONTRECORD

In commit ff9f111bce24 I mixed up inconsistent definitions of the LSN of
the first record in a page, when the previous record ends exactly at the
page boundary.  The correct LSN is adjusted to skip the WAL page header;
I failed to use that when setting XLogReaderState->overwrittenRecPtr,
so at WAL replay time VerifyOverwriteContrecord would refuse to let
replay continue past that record.

Backpatch to 10.  9.6 also contains this bug, but it's no longer being
maintained.

Discussion: https://postgr.es/m/45597.1637694259@sss.pgh.pa.us
src/backend/access/transam/xlogreader.c