diff options
| author | Noah Misch <noah@leadboat.com> | 2024-04-29 10:24:56 -0700 |
|---|---|---|
| committer | Noah Misch <noah@leadboat.com> | 2024-04-29 10:25:00 -0700 |
| commit | 70cadfba0c70b25922d0739a9e09d24f0efd7f46 (patch) | |
| tree | 245778aa706a272c45bc41875b3628dfed7702bb /src/backend/executor | |
| parent | 440b6251b75220bd28c063f50f5031f2004758f6 (diff) | |
| download | postgresql-70cadfba0c70b25922d0739a9e09d24f0efd7f46.tar.gz postgresql-70cadfba0c70b25922d0739a9e09d24f0efd7f46.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')
0 files changed, 0 insertions, 0 deletions