v10-0007-add-fixme-comment-about-pg_upgrade.patch
text/x-patch
Filename: v10-0007-add-fixme-comment-about-pg_upgrade.patch
Type: text/x-patch
Part: 6
Message:
Re: POC: make mxidoff 64 bits
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: format-patch
Series: patch v10-0007
Subject: add fixme comment about pg_upgrade
| File | + | − |
|---|---|---|
| src/backend/access/transam/multixact.c | 1 | 0 |
From 6c97887738164fc6810781211fba4774a63e3167 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas <heikki.linnakangas@iki.fi> Date: Wed, 18 Dec 2024 12:00:30 +0200 Subject: [PATCH v10 07/14] add fixme comment about pg_upgrade --- src/backend/access/transam/multixact.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/backend/access/transam/multixact.c b/src/backend/access/transam/multixact.c index 737154814a8..651766a4935 100644 --- a/src/backend/access/transam/multixact.c +++ b/src/backend/access/transam/multixact.c @@ -1302,6 +1302,7 @@ GetMultiXactIdMembers(MultiXactId multi, MultiXactMember **members, * we have just for this; the process in charge will signal the CV as soon * as it has finished writing the multixact offset. * + * FIXME: case 3 is now only needed for pg_upgraded clusters * 3. Because GetNewMultiXactId increments offset zero to offset one to * handle case #2, there is an ambiguity near the point of offset * wraparound. If we see next multixact's offset is one, is that our -- 2.39.5