public inbox for [email protected]  

help / color / mirror / Atom feed

Re: Test cluster with high OIDs above the signed-int limit (2B+)
3+ messages / 2 participants
[nested] [flat]

* Re: Test cluster with high OIDs above the signed-int limit (2B+)
@ 2026-04-20 13:29 Tom Lane <[email protected]>
  2026-04-20 13:39 ` Re: Test cluster with high OIDs above the signed-int limit (2B+) Dominique Devienne <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2026-04-20 13:29 UTC (permalink / raw)
  To: Dominique Devienne <[email protected]>; +Cc: pgsql-general

Dominique Devienne <[email protected]> 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






^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Test cluster with high OIDs above the signed-int limit (2B+)
  2026-04-20 13:29 Re: Test cluster with high OIDs above the signed-int limit (2B+) Tom Lane <[email protected]>
@ 2026-04-20 13:39 ` Dominique Devienne <[email protected]>
  2026-04-20 13:42   ` Re: Test cluster with high OIDs above the signed-int limit (2B+) Tom Lane <[email protected]>
  0 siblings, 1 reply; 3+ messages in thread

From: Dominique Devienne @ 2026-04-20 13:39 UTC (permalink / raw)
  To: Tom Lane <[email protected]>; +Cc: pgsql-general

On Mon, Apr 20, 2026 at 3:29 PM Tom Lane <[email protected]> wrote:
> Dominique Devienne <[email protected]> writes:
>
> See pg_resetwal --next-oid.  Don't recall what else you need to say
> to avoid breaking the cluster in other ways.

Great, thanks Tom.

So I just initdb, run the above, then start the cluster? That's it?






^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Test cluster with high OIDs above the signed-int limit (2B+)
  2026-04-20 13:29 Re: Test cluster with high OIDs above the signed-int limit (2B+) Tom Lane <[email protected]>
  2026-04-20 13:39 ` Re: Test cluster with high OIDs above the signed-int limit (2B+) Dominique Devienne <[email protected]>
@ 2026-04-20 13:42   ` Tom Lane <[email protected]>
  0 siblings, 0 replies; 3+ messages in thread

From: Tom Lane @ 2026-04-20 13:42 UTC (permalink / raw)
  To: Dominique Devienne <[email protected]>; +Cc: pgsql-general

Dominique Devienne <[email protected]> writes:
> On Mon, Apr 20, 2026 at 3:29 PM Tom Lane <[email protected]> wrote:
>> See pg_resetwal --next-oid.  Don't recall what else you need to say
>> to avoid breaking the cluster in other ways.

> So I just initdb, run the above, then start the cluster? That's it?

Right.  As I said, I don't recall what other options you might
need, but that's the game plan.

			regards, tom lane






^ permalink  raw  reply  [nested|flat] 3+ messages in thread

end of thread, other threads:[~2026-04-20 13:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-04-20 13:29 Re: Test cluster with high OIDs above the signed-int limit (2B+) Tom Lane <[email protected]>
2026-04-20 13:39 ` Dominique Devienne <[email protected]>
2026-04-20 13:42   ` Tom Lane <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox