WAL-log inplace update before revealing it to other sessions.
authorNoah Misch <noah@leadboat.com>
Fri, 25 Oct 2024 13:51:03 +0000 (06:51 -0700)
committerNoah Misch <noah@leadboat.com>
Fri, 25 Oct 2024 13:51:03 +0000 (06:51 -0700)
commit8e7e672cdaa6bfec85d4d5dd9be84159df23bb41
treedb340a3e67adf8734d1375377b0484c7532d95f6
parent243e9b40f1b2dd09d6e5bf91ebf6e822a2cd3704
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.92.nmisch@google.com
src/backend/access/heap/README.tuplock
src/backend/access/heap/heapam.c