From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dominique Devienne <ddevienne@gmail.com>
cc: pgsql-general@postgresql.org
Subject: Re: Test cluster with high OIDs above the signed-int limit (2B+)
In-reply-to: <CAFCRh--J4F0hFm_+x4rwW5eLEZnz_fNcp05Q1whO4YoKnQgJpg@mail.gmail.com>
References: <CAFCRh--J4F0hFm_+x4rwW5eLEZnz_fNcp05Q1whO4YoKnQgJpg@mail.gmail.com>
Comments: In-reply-to Dominique Devienne <ddevienne@gmail.com>
	message dated "Mon, 20 Apr 2026 11:44:46 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <195463.1776691778.1@sss.pgh.pa.us>
Date: Mon, 20 Apr 2026 09:29:38 -0400
Message-ID: <195464.1776691778@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/195464.1776691778%40sss.pgh.pa.us>
Precedence: bulk

Dominique Devienne <ddevienne@gmail.com> writes:
> 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.
> I'm moving into creating clusters on-the-fly for testing, and would
> like to force that situation to avoid a future silent regression,
> since it takes a long time to cross that threshold, and we do move up
> in major versions, so the over-the-threshold cluster will be
> abandoned. How can I achieve that?

See pg_resetwal --next-oid.  Don't recall what else you need to say
to avoid breaking the cluster in other ways.

			regards, tom lane