From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: LEMAIRE Leslie (Chargée de mission) - 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
Date: Wed, 4 May 2022 12:17:46 +0200
Message-ID: <202205041017.uc3dxylntais@alvherre.pgsql> (raw)
In-Reply-To: <f74d69e151b22171e8829551b1159e77@developpement-durable.gouv.fr>
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: alvherre@alvh.no-ip.org, leslie.lemaire@developpement-durable.gouv.fr, pgsql-bugs@lists.postgresql.org
Subject: Re: Implicitly created operator family not listed by pg_event_trigger_ddl_commands
In-Reply-To: <202205041017.uc3dxylntais@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox