Re: Translation of the NextOID message in pg_controldata

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Translation of the NextOID message in pg_controldata
Date: 2026-09-14 07:08:10
Message-ID: aqedWuHgzxirUrLo@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 uin32 ...

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.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-09-14 07:19:03 Fix unnecessary shared memory page allocation in CalculateShmemSize()
Previous Message Michael Paquier 2026-09-14 07:06:04 Re: Add a permission check to pg_stat_get_backend_subxact()