diff options
| author | Heikki Linnakangas | 2026-01-15 11:34:50 +0000 |
|---|---|---|
| committer | Heikki Linnakangas | 2026-01-15 11:34:50 +0000 |
| commit | c4b71e6f60c005b54bd025ee30aaee3f22496622 (patch) | |
| tree | d9e1b5b92143dce3bcddcf2ed6cc16f8e3d6eff2 /src/include/commands/sequence_xlog.h | |
| parent | da265a87175be469db6c178b57862ad1fb26dd04 (diff) | |
With 64-bit multixact offsets, PerformMembersTruncation() doesn't need
the starting offset anymore. The 'oldestOffset' value that
TruncateMultiXact() calculates is no longer used for anything. Remove
it, and the code to calculate it.
'oldestOffset' was included in the WAL record as 'startTruncMemb',
which sounds nice if you e.g. look at the WAL with pg_waldump, but it
was also confusing because we didn't actually use the value for
determining what to truncate. Replaying the WAL would remove all
segments older than 'endTruncMemb', regardless of
'startTruncMemb'. The 'startTruncOff' stored in the WAL record was
similarly unnecessary even before 64-bit multixid offsets, it was
stored just for the sake of symmetry with 'startTruncMemb'. Remove
both from the WAL record, and rename the remaining 'endTruncOff' to
'oldestMulti' and 'endTruncMemb' to 'oldestOffset', for consistency
with the variable names used for them in other places.
Reviewed-by: Andrey Borodin <x4mmm@yandex-team.ru>
Discussion: https://www.postgresql.org/message-id/000301b2-5b81-4938-bdac-90f6eb660843@iki.fi
Diffstat (limited to 'src/include/commands/sequence_xlog.h')
0 files changed, 0 insertions, 0 deletions
