aboutsummaryrefslogtreecommitdiff
path: root/src/fe_utils/string_utils.c
diff options
context:
space:
mode:
authorNoah Misch <noah@leadboat.com>2025-01-25 11:28:14 -0800
committerNoah Misch <noah@leadboat.com>2025-01-25 11:28:19 -0800
commitdc02b98bd1c8d653370fd8828063b1aee0b5b9eb (patch)
treea4c663adeecff50c8edc8a17471c59a02141d930 /src/fe_utils/string_utils.c
parent216294ba592fdfaa38bdf9767527f8424bd29b14 (diff)
downloadpostgresql-dc02b98bd1c8d653370fd8828063b1aee0b5b9eb.tar.gz
postgresql-dc02b98bd1c8d653370fd8828063b1aee0b5b9eb.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/fe_utils/string_utils.c')
0 files changed, 0 insertions, 0 deletions