Re: Implicitly created operator family not listed by pg_event_trigger_ddl_commands - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: Implicitly created operator family not listed by pg_event_trigger_ddl_commands
Date
Msg-id 202205201412.jrrbxaotej3z@alvherre.pgsql
Whole thread Raw
In response to Re: Implicitly created operator family not listed by pg_event_trigger_ddl_commands  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Implicitly created operator family not listed by pg_event_trigger_ddl_commands
List pgsql-bugs
On 2022-May-20, Masahiko Sawada wrote:

> 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.

Oh, hahah.  Hmm, I feel inclined to add the trigger rather than remove
the lines from the expected output.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"La rebeldía es la virtud original del hombre" (Arthur Schopenhauer)



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17490: unconsistency between TRUNCATE RESTART IDENTITY and setval()
Next
From: Tom Lane
Date:
Subject: Re: BUG #17486: [pg_restore] Restoring a view fails if this view contains an attribute without alias name.