WAL-log inplace update before revealing it to other sessions.
authorNoah Misch
Fri, 25 Oct 2024 13:51:03 +0000 (06:51 -0700)
committerNoah Misch
Fri, 25 Oct 2024 13:51:06 +0000 (06:51 -0700)
commitbfd5c6e279c8e1702eea882439dc7ebdf4d4b3a5
tree418896f4d63f386f8c4353207dff643913c663dc
parent95c5acb3fc261067ab65ddc0b2dca8e162f09442
WAL-log inplace update before revealing it to other sessions.

A buffer lock won't stop a reader having already checked tuple
visibility.  If a vac_update_datfrozenid() and then a crash happened
during inplace update of a relfrozenxid value, datfrozenxid could
overtake relfrozenxid.  That could lead to "could not access status of
transaction" errors.  Back-patch to v12 (all supported versions).  In
v14 and earlier, this also back-patches the assertion removal from
commit 7fcf2faf9c7dd473208fd6d5565f88d7f733782b.

Discussion: https://postgr.es/m/20240620012908[email protected]
src/backend/access/heap/README.tuplock
src/backend/access/heap/heapam.c