Date: Wed, 4 May 2022 12:17:46 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: LEMAIRE Leslie =?utf-8?Q?=28Charg=C3=A9e_de_mission?=
	=?utf-8?Q?=29?= - SG/SNUM/UNI/DRC
 <leslie.lemaire@developpement-durable.gouv.fr>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Implicitly created operator family not listed by
 pg_event_trigger_ddl_commands
Message-ID: <202205041017.uc3dxylntais@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <f74d69e151b22171e8829551b1159e77@developpement-durable.gouv.fr>
Archived-At: 
 <https://www.postgresql.org/message-id/202205041017.uc3dxylntais%40alvherre.pgsql>
Precedence: bulk

On 2022-May-02, LEMAIRE Leslie (Chargée de mission) - SG/SNUM/UNI/DRC wrote:

> As stated in the documentation [1], creating an operator class without
> specifying the FAMILY option will create an operator family with the same
> name as the new class if it doesn't already exist. In this case, my event
> trigger is activated through the "CREATE OPERATOR CLASS" tag as usual, but
> pg_event_trigger_ddl_commands() still returns only one row - for the
> operator class creation. I would have expected it to list the creation of
> the operator family as well.

I agree, this looks like an omission somewhere -- the extra object
should have been reported.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/