MIME-Version: 1.0
References: <CAFCRh--J4F0hFm_+x4rwW5eLEZnz_fNcp05Q1whO4YoKnQgJpg@mail.gmail.com>
 <CANzqJaC40fS+bHNbPVjmSbRwdNHs8ZbxPUbDrJeC2hFyB9z0FQ@mail.gmail.com> <CAFCRh-931skmWJtK7m09jVUAV4aEFDFndaCC_d8HBQCoNmtHoQ@mail.gmail.com>
In-Reply-To: <CAFCRh-931skmWJtK7m09jVUAV4aEFDFndaCC_d8HBQCoNmtHoQ@mail.gmail.com>
From: Dominique Devienne <ddevienne@gmail.com>
Date: Mon, 20 Apr 2026 15:08:35 +0200
Message-ID: <CAFCRh-_NEPF+WZyL90fTjA5dpETeqb70rC+Sb4X+QX+cpdgQnw@mail.gmail.com>
Subject: Re: Test cluster with high OIDs above the signed-int limit (2B+)
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAFCRh-_NEPF%2BWZyL90fTjA5dpETeqb70rC%2BSb4X%2BQX%2BcpdgQnw%40mail.gmail.com>
Precedence: bulk

On Mon, Apr 20, 2026 at 2:59=E2=80=AFPM Dominique Devienne <ddevienne@gmail=
.com> 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".