From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: =?iso-8859-1?Q?=C1lvaro?= Herrera <alvherre@kurilemu.de>,
        Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
        pgsql-hackers@lists.postgresql.org
Subject: Re: Translation of the NextOID message in pg_controldata
In-reply-to: <aqedWuHgzxirUrLo@paquier.xyz>
References: <aqeNcd4403BGVZqc@paquier.xyz> <aqeO1OU7uZjhioAq@alvherre.pgsql>
 <aqedWuHgzxirUrLo@paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
	message dated "Mon, 14 Sep 2026 16:08:10 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <109493.1789394228.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Sep 2026 09:57:08 -0400
Message-ID: <109494.1789394228@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/109494.1789394228%40sss.pgh.pa.us>
Precedence: bulk

Michael Paquier <michael@paquier.xyz> writes:
> On Mon, Sep 14, 2026 at 08:41:59AM +0200, Alvaro Herrera wrote:
>> I'm not sure I understand why we care that we hardcode that Oid8 is the
>> same as uint64.  It's never been a problem that Oid is the same as uin3=
2 ...

> For me, the reason is greppability of oid8 information as the
> variables printed in the strings may not refer to variables declared
> in the code.

Yeah.  It's not a big deal, so maybe PRIu64 is the best option.
I just wanted to be sure we'd considered whether there's another way.

			regards, tom lane