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:08:35 +0200
Message-ID: <CAFCRh-_NEPF+WZyL90fTjA5dpETeqb70rC+Sb4X+QX+cpdgQnw@mail.gmail.com> (raw)
In-Reply-To: <CAFCRh-931skmWJtK7m09jVUAV4aEFDFndaCC_d8HBQCoNmtHoQ@mail.gmail.com>
References: <CAFCRh--J4F0hFm_+x4rwW5eLEZnz_fNcp05Q1whO4YoKnQgJpg@mail.gmail.com>
<CANzqJaC40fS+bHNbPVjmSbRwdNHs8ZbxPUbDrJeC2hFyB9z0FQ@mail.gmail.com>
<CAFCRh-931skmWJtK7m09jVUAV4aEFDFndaCC_d8HBQCoNmtHoQ@mail.gmail.com>
On Mon, Apr 20, 2026 at 2:59 PM Dominique Devienne <[email protected]> wrote:
> No. I don't even remember the exact bug
Was an old test using lo_creat(-1) RETURNING the OID, and code doing
`std::stoi(PQgetvalue(...))`. In production we don't use LO and use
the binary protocol, so no such issue, still my original point
remains. We process OIDs in several places, and making sure our test
suite works with high OIDs would be better. If I fully control the
cluster, which is created specifically for the test run, on-the-fly,
it's like to be able to similate high OIDs "instantly".
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-_NEPF+WZyL90fTjA5dpETeqb70rC+Sb4X+QX+cpdgQnw@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