public inbox for [email protected]
help / color / mirror / Atom feedFrom: 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 15:30:53 +0200
Message-ID: <CAFCRh-_8qobQf7MDPFAo0qytSK78W+ugY03JXzbJ5++X+v0HJA@mail.gmail.com> (raw)
In-Reply-To: <CANzqJaAWuD+JBk03Q02=UBLAPBsOonyww7xsPon9Op_zk-4EDw@mail.gmail.com>
References: <CAFCRh--J4F0hFm_+x4rwW5eLEZnz_fNcp05Q1whO4YoKnQgJpg@mail.gmail.com>
<CANzqJaC40fS+bHNbPVjmSbRwdNHs8ZbxPUbDrJeC2hFyB9z0FQ@mail.gmail.com>
<CAFCRh-931skmWJtK7m09jVUAV4aEFDFndaCC_d8HBQCoNmtHoQ@mail.gmail.com>
<CAFCRh-_NEPF+WZyL90fTjA5dpETeqb70rC+Sb4X+QX+cpdgQnw@mail.gmail.com>
<CANzqJaAWuD+JBk03Q02=UBLAPBsOonyww7xsPon9Op_zk-4EDw@mail.gmail.com>
On Mon, Apr 20, 2026 at 3:23 PM Ron Johnson <[email protected]> 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.
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-_8qobQf7MDPFAo0qytSK78W+ugY03JXzbJ5++X+v0HJA@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