summaryrefslogtreecommitdiff
path: root/doc/src/sgml/func.sgml
diff options
context:
space:
mode:
authorNoah Misch2024-10-24 16:16:38 +0000
committerNoah Misch2024-10-24 16:16:38 +0000
commit67bab53d64428e4d43386be0e077cd662bc9cad3 (patch)
tree777530ecd4bafb42832e2aa8de1c5b7a0954435e /doc/src/sgml/func.sgml
parente947224cbbceca535fd00001ba459417e6917d1b (diff)
Fix parallel worker tracking of new catalog relfilenumbers.
Reunite RestorePendingSyncs() with RestoreRelationMap(). If RelationInitPhysicalAddr() ran after RestoreRelationMap() but before RestorePendingSyncs(), the relcache entry could cause RelationNeedsWAL() to return true erroneously. Trouble required commands of the current transaction to include REINDEX or CLUSTER of a system catalog. The parallel leader correctly derived RelationNeedsWAL()==false from the new relfilenumber, but the worker saw RelationNeedsWAL()==true. Worker MarkBufferDirtyHint() then wrote unwanted WAL. Recovery of that unwanted WAL could lose tuples like the system could before commit c6b92041d38512a4176ed76ad06f713d2e6c01a8 introduced this tracking. RestorePendingSyncs() and RestoreRelationMap() were adjacent till commit 126ec0bc76d044d3a9eb86538b61242bf7da6db4, so no back-patch for now. Reviewed by Tom Lane. Discussion: https://postgr.es/m/[email protected]
Diffstat (limited to 'doc/src/sgml/func.sgml')
0 files changed, 0 insertions, 0 deletions