Re: Implicitly created operator family not listed by pg_event_trigger_ddl_commands

On Fri, May 20, 2022 at 7:57 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> On 2022-May-20, Michael Paquier wrote:
>
> > That seems fine, at quick glance. Thanks for the patch!

Thank you for updating the patch!

>
> Unfortunately, the tests don't pass in versions 10-13, so I'm
> investigating what's up with that.

I got the failure when testing in 13:

@@ -429,8 +429,6 @@
-- CREATE OPERATOR CLASS without FAMILY clause should report
-- both CREATE OPERATOR FAMILY and CREATE OPERATOR CLASS
CREATE OPERATOR CLASS evttrigopclass FOR TYPE int USING btree AS STORAGE int;
-NOTICE: END: command_tag=CREATE OPERATOR FAMILY type=operator family
identity=public.evttrigopclass USING btree
-NOTICE: END: command_tag=CREATE OPERATOR CLASS type=operator class
identity=public.evttrigopclass USING btree
DROP EVENT TRIGGER regress_event_trigger_report_dropped;
-- only allowed from within an event trigger function, should fail
select pg_event_trigger_table_rewrite_oid();

I think that the event trigger that emits these NOTICE messages
doesn't exist in 13 or older branches. It was added by 2d689babe3c.

Regards,

--
Masahiko Sawada
EDB: https://www.enterprisedb.com/