Re: DISABLE TRIGGER doc wrong?

Ron <ronljohnsonjr@gmail.com>

From: Ron Johnson <ronljohnsonjr@gmail.com>
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2025-08-26T12:53:37Z
Lists: pgsql-general
On Tue, Aug 26, 2025 at 3:01 AM Dominique Devienne <ddevienne@gmail.com>
wrote:
[snip]

> ERROR:  permission denied: "RI_ConstraintTrigger_c_1226298044" is a
> system trigger
>
> (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.
And it can seem quite random to someone who doesn't dig into the source
code.  For example, a couple of years ago, I installed PG14 on 5
newly-built servers.  The OIDs of the ten databases I created on them were:

Srv 1: 19762693,  544452602
Srv 2:  1002727,   11988067
Srv 3:    16388,  509694991
Srv 4:    16387, 1805148571
Srv 5:    16388, 3046645364

(Too bad Postgresql doesn't have CREATED_ON timestamp, CREATED_BY oid,
MODIFIED_ON timestamp and MODIFIED_BY oid fields in pg_database and
pg_class,to verify whether my memory is correct.  The counter-argument when
I requested such fields was "pg_dump/pg_upgrade creates new objects, so
it's not _really_ when they were created" and "you don't _really_ need
those fields".)

-- 
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!