Re: Test cluster with high OIDs above the signed-int limit (2B+)

From: Dominique Devienne <ddevienne(at)gmail(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Test cluster with high OIDs above the signed-int limit (2B+)
Date: 2026-04-20 13:30:53
Message-ID: CAFCRh-_8qobQf7MDPFAo0qytSK78W+ugY03JXzbJ5++X+v0HJA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Apr 20, 2026 at 3:23 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
> It's an unsigned integer, so I'd say not use signed ints when processing OIDs.

Well duh, that's why it's a bug.
But it's a sneaky bug, because clusters rarely enter that high-OID territory.
That's precisely why I'd like a way to provoke it.

> It's a valid question, though, what happens when the OID counter wraps around and hits a duplicate.

Again, I'm NOT interested in OID wrap-around. But the "second-half" of
the OID space.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dominique Devienne 2026-04-20 13:39:47 Re: Test cluster with high OIDs above the signed-int limit (2B+)
Previous Message Greg Sabino Mullane 2026-04-20 13:29:56 Re: Test cluster with high OIDs above the signed-int limit (2B+)