diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2021-11-26 11:14:27 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2021-11-26 11:14:27 -0300 |
| commit | 9c6ab1ef338273850c8c33f808d27486d3c5ad76 (patch) | |
| tree | aea2eff1a8710c29e280886e3f3c6da97fbc0995 /contrib/btree_gist/expected | |
| parent | 0d335cbd5c63009576280ff502b31a84e353a86b (diff) | |
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
Diffstat (limited to 'contrib/btree_gist/expected')
0 files changed, 0 insertions, 0 deletions