Horton

Re: Implicitly created operator family not listed by pg_event_trigger_ddl_commands

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Amit Kapila <amit.kapila16@gmail.com>, LEMAIRE Leslie (Chargée de mission) - SG/SNUM/UNI/DRC <leslie.lemaire@developpement-durable.gouv.fr>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-05-20T14:12:01Z
Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix DDL deparse of CREATE OPERATOR CLASS

  2. Backpatch regression tests added by 2d689babe3cb

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)