public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dominique Devienne <[email protected]>
To: Ron Johnson <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Test cluster with high OIDs above the signed-int limit (2B+)
Date: Mon, 20 Apr 2026 14:59:51 +0200
Message-ID: <CAFCRh-931skmWJtK7m09jVUAV4aEFDFndaCC_d8HBQCoNmtHoQ@mail.gmail.com> (raw)
In-Reply-To: <CANzqJaC40fS+bHNbPVjmSbRwdNHs8ZbxPUbDrJeC2hFyB9z0FQ@mail.gmail.com>
References: <CAFCRh--J4F0hFm_+x4rwW5eLEZnz_fNcp05Q1whO4YoKnQgJpg@mail.gmail.com>
	<CANzqJaC40fS+bHNbPVjmSbRwdNHs8ZbxPUbDrJeC2hFyB9z0FQ@mail.gmail.com>

On Mon, Apr 20, 2026 at 2:45 PM Ron Johnson <[email protected]> wrote:
> On Mon, Apr 20, 2026 at 5:45 AM Dominique Devienne <[email protected]> wrote:
>> Hi. A few weeks ago, one of our clusters, with high DDL churn from
>> UTs, crossed the 2B mark for OIDs, which exposed a bug in our code.
>
> Because you track and remember OIDs?

No. I don't even remember the exact bug, and we lost networking to our
SCM right now, so can't even look it up (obviously it's not
decentralized SCM). But signed vs unsigned and 2B+ is a classic bug,
worth testing for, except it's impractical to reach such high OIDs on
demand. Given there's a cluster-wide OID counter, surely there's a
way, even hackish, to influence that counter, no? PostgreSQL itself
has mitigation strategies when running out of OIDs, doesn't it? It's a
different use-case, but that implies also reaching large OIDs, and I
suspect this is unit tested, no?

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Test cluster with high OIDs above the signed-int limit (2B+)
  In-Reply-To: <CAFCRh-931skmWJtK7m09jVUAV4aEFDFndaCC_d8HBQCoNmtHoQ@mail.gmail.com>

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

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