Re: Test cluster with high OIDs above the signed-int limit (2B+)
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dominique Devienne <ddevienne@gmail.com>
Cc: pgsql-general@postgresql.org
Date: 2026-04-20T13:29:38Z
Lists: pgsql-general
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