pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Masahiko Sawada <msawada@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Report next_multi_offset as bigint in pg_control_checkpoint().
Date: Thu, 27 Aug 2026 19:26:56 +0000
Message-ID: <E1wzfkV-00000002NqE-1OFI@gemulon.postgresql.org> (raw)

Report next_multi_offset as bigint in pg_control_checkpoint().

Commit bd8d9c9bdfa widened MultiXactOffset to 64 bits, but
pg_control_checkpoint() still handle checkPointCopy.nextMultiOffset as
xid type and declared next_multi_offset column as xid. Since xid is 32
bits wide, an offset above 2^32 was reported truncated, while
pg_controldata printed the full value of the same field.

This commit reports the column as bigint instead. That matches
pg_get_multixact_stats(), which already reports num_members and
members_size, both derived from these same offsets, as int8.

Backpatch to v19, where MultiXactOffset was widened.

Bump catalog version.

Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi>
Reviewed-by: Chao Li <li.evan.chao@gmail.com>
Discussion: https://postgr.es/m/CAD21AoCvzerscfU8o4ARQ793yAGHpQ72r2x5apeC_W2-k=SLCQ@mail.gmail.com
Backpatch-through: 19

Branch
------
REL_19_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/3fcb7167198e1b2ecf8cc0d934c8ffe53755e0ae

Modified Files
--------------
doc/src/sgml/func/func-info.sgml        | 2 +-
src/backend/utils/misc/pg_controldata.c | 2 +-
src/include/catalog/catversion.h        | 2 +-
src/include/catalog/pg_proc.dat         | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)



view thread (2+ messages)

Message-ID: <E1wzfkV-00000002NqE-1OFI@gemulon.postgresql.org>
Permalink:  ../E1wzfkV-00000002NqE-1OFI@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1wzfkV-00000002NqE-1OFI@gemulon.postgresql.org

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: msawada@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Report next_multi_offset as bigint in pg_control_checkpoint().
  In-Reply-To: <E1wzfkV-00000002NqE-1OFI@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox