diff options
| author | Noah Misch | 2025-12-17 00:13:54 +0000 |
|---|---|---|
| committer | Noah Misch | 2025-12-17 00:13:56 +0000 |
| commit | 0dfbd191a939d6307cd7e3e1c69c7dcf3a17a65e (patch) | |
| tree | de976d361fa6a945ae86816e2b4a02b795c00bc1 /src/fe_utils/parallel_slot.c | |
| parent | e4b1986b9899fedc50c99738f85da39e65e4743f (diff) | |
Assert lack of hazardous buffer locks before possible catalog read.REL_14_STABLE
Commit 0bada39c83a150079567a6e97b1a25a198f30ea3 fixed a bug of this kind,
which existed in all branches for six days before detection. While the
probability of reaching the trouble was low, the disruption was extreme. No
new backends could start, and service restoration needed an immediate
shutdown. Hence, add this to catch the next bug like it.
The new check in RelationIdGetRelation() suffices to make autovacuum detect
the bug in commit 243e9b40f1b2dd09d6e5bf91ebf6e822a2cd3704 that led to commit
0bada39. This also checks in a number of similar places. It replaces each
Assert(IsTransactionState()) that pertained to a conditional catalog read.
Back-patch to v14 - v17. This a back-patch of commit
f4ece891fc2f3f96f0571720a1ae30db8030681b (from before v18 branched) to
all supported branches, to accompany the back-patch of commits 243e9b4
and 0bada39. For catalog indexes, the bttextcmp() behavior that
motivated IsCatalogTextUniqueIndexOid() was v18-specific. Hence, this
back-patch doesn't need that or its correction from commit
4a4ee0c2c1e53401924101945ac3d517c0a8a559.
Reported-by: Alexander Lakhin <exclusion@gmail.com>
Discussion: https://postgr.es/m/20250410191830.0e.nmisch@google.com
Discussion: https://postgr.es/m/10ec0bc3-5933-1189-6bb8-5dec4114558e@gmail.com
Backpatch-through: 14-17
Diffstat (limited to 'src/fe_utils/parallel_slot.c')
0 files changed, 0 insertions, 0 deletions