pgsql: Fix multixact members truncation at page boundary - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: Fix multixact members truncation at page boundary
Date
Msg-id E1x6omZ-00000000aPy-0Yaj@gemulon.postgresql.org
Whole thread
List pgsql-committers
Fix multixact members truncation at page boundary

Like in PerformOffsetsTruncation() and e.g. in TruncateSUBTRANS(),
need to step back to previous page at page boundary, to avoid passing
a cutoff page to SimpleLruTruncate() that hasn't been created
yet. Otherwise you can get a bogus 'LOG: could not truncate directory
"pg_multixact/members": apparent wraparound' message in the log.

Reported-by: Noah Misch <noah@leadboat.com>
Discussion: https://www.postgresql.org/message-id/20260827231757.78.noahmisch@microsoft.com
Backpatch-through: 19

Branch
------
REL_19_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/d8408e8d6823036bb88310b36eed8d9607220847

Modified Files
--------------
src/backend/access/transam/multixact.c | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)


pgsql-committers by date:

Previous
From: Manuel Reyes Bravo
Date:
Subject: Re: pgsql: Fix index rebuild progress reporting for REPACK (CONCURRENTLY)
Next
From: Robert Haas
Date:
Subject: pgsql: pg_plan_advice: Disallow empty sublists within JOIN_ORDER()