Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1uquAy-00EyVW-Kq
	for pgsql-general@arkaria.postgresql.org; Tue, 26 Aug 2025 13:57:30 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1uquAy-006dBP-2E
	for pgsql-general@arkaria.postgresql.org; Tue, 26 Aug 2025 13:57:28 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uquAx-006dBH-OM
	for pgsql-general@lists.postgresql.org; Tue, 26 Aug 2025 13:57:28 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uquAv-001xjK-2m
	for pgsql-general@lists.postgresql.org;
	Tue, 26 Aug 2025 13:57:28 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 57QDvMMD1057303;
	Tue, 26 Aug 2025 09:57:22 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron Johnson <ronljohnsonjr@gmail.com>
cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: DISABLE TRIGGER doc wrong?
In-reply-to: <CANzqJaA_UfXQZoEu7bh6=khERBUixJOAj2SscMua-uv=uFSxeg@mail.gmail.com>
References: <CAFCRh--VRAHh2D7PsvW1mgRFfx2bqLQH_8asEBTLBn3RDLT7tA@mail.gmail.com> <185dd861-4e5a-47c0-9f2e-84dfa8a406ca@postgrespro.ru> <CAFCRh-85iWNy51sQBiVtwE=xq_pEhqR_cOetTa0-DK9TCjqQyw@mail.gmail.com> <26239cd6-a13d-4137-9f1d-61e18c4cf0e6@aklaver.com> <CAFCRh-8hUbi26hfD5ev4A7UwNAOhnmHf-JFpsk0StTmvaFC=Yg@mail.gmail.com> <CANzqJaCHmh+q4GqJSXir9nXLiHVY7MWgPo4n2xaMSCwwxE5hfQ@mail.gmail.com> <CAFCRh-9hgN5r+PL2AUJqnx-LwpckYd-nHRdCBajAonUJFo2fnQ@mail.gmail.com> <CANzqJaA_UfXQZoEu7bh6=khERBUixJOAj2SscMua-uv=uFSxeg@mail.gmail.com>
Comments: In-reply-to Ron Johnson <ronljohnsonjr@gmail.com>
	message dated "Tue, 26 Aug 2025 09:08:35 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1057301.1756216642.1@sss.pgh.pa.us>
Date: Tue, 26 Aug 2025 09:57:22 -0400
Message-ID: <1057302.1756216642@sss.pgh.pa.us>
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/1057302.1756216642%40sss.pgh.pa.us>
Precedence: bulk

Ron Johnson <ronljohnsonjr@gmail.com> 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