diff options
author | Noah Misch <noah@leadboat.com> | 2025-01-25 11:28:14 -0800 |
---|---|---|
committer | Noah Misch <noah@leadboat.com> | 2025-01-25 11:28:19 -0800 |
commit | 25e99483c4116313b678cc94df53d3ea28977752 (patch) | |
tree | faad3e59f6d02b27387492024628519a4c687466 /src/backend/executor/nodeModifyTable.c | |
parent | 7b3259bd7cf37da472ff5c2ce25fe0aa552e6fe0 (diff) | |
download | postgresql-25e99483c4116313b678cc94df53d3ea28977752.tar.gz postgresql-25e99483c4116313b678cc94df53d3ea28977752.zip |
At update of non-LP_NORMAL TID, fail instead of corrupting page header.
The right mix of DDL and VACUUM could corrupt a catalog page header such
that PageIsVerified() durably fails, requiring a restore from backup.
This affects only catalogs that both have a syscache and have DDL code
that uses syscache tuples to construct updates. One of the test
permutations shows a variant not yet fixed.
This makes !TransactionIdIsValid(TM_FailureData.xmax) possible with
TM_Deleted. I think core and PGXN are indifferent to that.
Per bug #17821 from Alexander Lakhin. Back-patch to v13 (all supported
versions). The test case is v17+, since it uses INJECTION_POINT.
Discussion: https://postgr.es/m/17821-dd8c334263399284@postgresql.org
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions