Close race condition between datfrozen and relfrozen updates.
authorNoah Misch <[email protected]>
Mon, 29 Apr 2024 17:24:56 +0000 (10:24 -0700)
committerNoah Misch <[email protected]>
Mon, 29 Apr 2024 17:25:00 +0000 (10:25 -0700)
commit2ca19aa8165c6bec84c1d527fc5f3100c2161b1a
tree3b87cbad052a06bfa7ae502cd4e1bb9b4dba60e6
parent617a23927249c78f23ef005aaa78b508570f4cc8
Close race condition between datfrozen and relfrozen updates.

vac_update_datfrozenxid() did multiple loads of relfrozenxid and
relminmxid from buffer memory, and it assumed each would get the same
value.  Not so if a concurrent vac_update_relstats() did an inplace
update.  Commit 2d2e40e3befd8b9e0d2757554537345b15fa6ea2 fixed the same
kind of bug in vac_truncate_clog().  Today's bug could cause the
rel-level field and XIDs in the rel's rows to precede the db-level
field.  A cluster having such values should VACUUM affected tables.
Back-patch to v12 (all supported versions).

Discussion: https://postgr.es/m/20240423003956[email protected]
src/backend/commands/vacuum.c