diff options
| author | Thomas Munro <tmunro@postgresql.org> | 2024-12-03 09:27:05 +1300 |
|---|---|---|
| committer | Thomas Munro <tmunro@postgresql.org> | 2024-12-03 10:19:47 +1300 |
| commit | d4ffbf47b2d43fe3319474970948f276c8e2f8c9 (patch) | |
| tree | 9c9eb345e473d4d9c66377289d99f7aad2b38413 /src/backend/executor/nodeProjectSet.c | |
| parent | a963abd549e9e2b518460ccf31ea3728214207c0 (diff) | |
| download | postgresql-d4ffbf47b2d43fe3319474970948f276c8e2f8c9.tar.gz postgresql-d4ffbf47b2d43fe3319474970948f276c8e2f8c9.zip | |
RelationTruncate() must set DELAY_CHKPT_START.
Previously, it set only DELAY_CHKPT_COMPLETE. That was important,
because it meant that if the XLOG_SMGR_TRUNCATE record preceded a
XLOG_CHECKPOINT_ONLINE record in the WAL, then the truncation would also
happen on disk before the XLOG_CHECKPOINT_ONLINE record was
written.
However, it didn't guarantee that the sync request for the truncation
was processed before the XLOG_CHECKPOINT_ONLINE record was written. By
setting DELAY_CHKPT_START, we guarantee that if an XLOG_SMGR_TRUNCATE
record is written to WAL before the redo pointer of a concurrent
checkpoint, the sync request queued by that operation must be processed
by that checkpoint, rather than being left for the following one.
This is a refinement of commit 412ad7a5563. Back-patch to all supported
releases, like that commit.
Author: Robert Haas <robertmhaas@gmail.com>
Reported-by: Thomas Munro <thomas.munro@gmail.com>
Discussion: https://postgr.es/m/CA%2BhUKG%2B-2rjGZC2kwqr2NMLBcEBp4uf59QT1advbWYF_uc%2B0Aw%40mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeProjectSet.c')
0 files changed, 0 insertions, 0 deletions