public inbox for [email protected]
help / color / mirror / Atom feedRe: DISABLE TRIGGER doc wrong?
2+ messages / 2 participants
[nested] [flat]
* Re: DISABLE TRIGGER doc wrong?
@ 2025-08-26 13:08 Ron Johnson <[email protected]>
2025-08-26 13:57 ` Re: DISABLE TRIGGER doc wrong? Tom Lane <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Ron Johnson @ 2025-08-26 13:08 UTC (permalink / raw)
To: pgsql-generallists.postgresql.org <[email protected]>
On Tue, Aug 26, 2025 at 9:01 AM Dominique Devienne <[email protected]>
wrote:
> On Tue, Aug 26, 2025 at 2:54 PM Ron Johnson <[email protected]>
> wrote:
> > On Tue, Aug 26, 2025 at 3:01 AM Dominique Devienne <[email protected]>
> wrote:
> >> ERROR: permission denied: "RI_ConstraintTrigger_c_1226298044" is a
> >> (yes, that's a large OID... For a 1 year old DB)
> >
> > PG's OID allocation of "user-land" OIDs doesn't start at 16384 anymore.
>
> This is a 17 cluster. So not even 1 year old then.
> So getting to 1.2B OIDs in 10 months,
> doesn't bode well for the longevity of that cluster.
> But we're getting OT here.
> This is not a "production" server, lots of CIs and manual testing there.
>
Like I said, it's not completely linear. The real question, though, is
whether PG looks for gaps in oid allocation once it wants to try and
allocate an oid of uint32 max.
I bet it does. If it doesn't... pg_dump/pg_restore, baby!
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: DISABLE TRIGGER doc wrong?
2025-08-26 13:08 Re: DISABLE TRIGGER doc wrong? Ron Johnson <[email protected]>
@ 2025-08-26 13:57 ` Tom Lane <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2025-08-26 13:57 UTC (permalink / raw)
To: Ron Johnson <[email protected]>; +Cc: pgsql-generallists.postgresql.org <[email protected]>
Ron Johnson <[email protected]> writes:
> Like I said, it's not completely linear. The real question, though, is
> whether PG looks for gaps in oid allocation once it wants to try and
> allocate an oid of uint32 max.
OID counter wraparound is not particularly a problem.
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-08-26 13:57 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-08-26 13:08 Re: DISABLE TRIGGER doc wrong? Ron Johnson <[email protected]>
2025-08-26 13:57 ` 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