aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorNoah Misch <noah@leadboat.com>2024-04-29 10:24:56 -0700
committerNoah Misch <noah@leadboat.com>2024-04-29 10:24:59 -0700
commit7c5915c4b16c965124a36615ec54cca501a212a9 (patch)
tree0150781ef111cc043c9ff0137956d69b8fc49103 /src/backend/executor/nodeFunctionscan.c
parent9b41d1d634aa9a3a36a21c5624b25c8475fd51ee (diff)
downloadpostgresql-7c5915c4b16c965124a36615ec54cca501a212a9.tar.gz
postgresql-7c5915c4b16c965124a36615ec54cca501a212a9.zip
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.e7.nmisch@google.com
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions