From: Tom Lane <tgl@sss.pgh.pa.us>
To: p2wap3@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18570: Drop event trigger for DDL finishes successfully but
 trigger still executed on DDL
In-reply-to: <18570-43bc1b85bebd2572@postgresql.org>
References: <18570-43bc1b85bebd2572@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 06 Aug 2024 08:53:19 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1344571.1722957085.1@sss.pgh.pa.us>
Date: Tue, 06 Aug 2024 11:11:25 -0400
Message-ID: <1344572.1722957085@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1344572.1722957085%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I created a function and an event trigger but then decided to drop the event
> trigger (w/o dropping the function yet).

DROP EVENT TRIGGER works as expected for me.  Can you provide
a fully self-contained example of what you did that didn't work?
The most obvious explanation is that you forgot to commit the DROP,
or something along that line.

> I double checked by querying the information_schema.triggers (the list is
> empty)

That proves exactly nothing, because event triggers are never shown
in that view anyway.  They are not a SQL-standard feature, but
information_schema is all about SQL-standard things.

psql's "\dy" command could be used to check for event triggers.

			regards, tom lane