Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ns3MZ-0002hb-7x for pgsql-bugs@arkaria.postgresql.org; Fri, 20 May 2022 14:12:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ns3MX-0001Hy-E6 for pgsql-bugs@arkaria.postgresql.org; Fri, 20 May 2022 14:12:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ns3MW-0001Hp-KO for pgsql-bugs@lists.postgresql.org; Fri, 20 May 2022 14:12:17 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ns3MO-0005ka-Qs for pgsql-bugs@lists.postgresql.org; Fri, 20 May 2022 14:12:16 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 94F0D3200976; Fri, 20 May 2022 10:12:04 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 20 May 2022 10:12:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1653055924; x=1653142324; bh=4 pxkzUVjLfxpIwTnCa7zyx0MEWeekx4bhW1U/y3zUPU=; b=EiXx5pH6cXnGEOIjB 69GPahlalaEgHFps7136/nsp8K0XcHIv0BgTpo0QM9Bu7FsQbS958Ms8oJ6UBTne N8k6CCkkgjl4up95PKgdgVWhM39yTElZdw1F+MREGiiExeIHSNzHNU2jobZ5s+NY +45X7aUgkNNd7HigvdWiFba5DneYGMpvSl+XKNgSk+wZb/ySd7uVA+NkTHMiXUsq fbhA9TDgqF6u2XZKuax8Q23NxUuSIYWn6FG5NomM/OLyrHAHqfTsMTKqu6PJlOCu rTP75kHHX64lMD5CY0ofkJ5MFcJjrERZSaYhrd01H6eWCC2wuvpT6ZNcCwHE/++A vBuRQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrieefgdejvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpedvkedtffduffdtffffheffhfejjefhgfeiueeukeejkeff gfdufffhudffffeuveenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 20 May 2022 10:12:03 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 1BD702A2204; Fri, 20 May 2022 16:12:01 +0200 (CEST) Date: Fri, 20 May 2022 16:12:01 +0200 From: Alvaro Herrera To: Masahiko Sawada Cc: Michael Paquier , Amit Kapila , LEMAIRE Leslie =?utf-8?Q?=28Charg=C3=A9e_de_mission?= =?utf-8?Q?=29?= - SG/SNUM/UNI/DRC , PostgreSQL mailing lists Subject: Re: Implicitly created operator family not listed by pg_event_trigger_ddl_commands Message-ID: <202205201412.jrrbxaotej3z@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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)