Feedback-ID: ia2694551:Fastmail
Date: Tue, 6 Aug 2024 10:38:38 -0400
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: p2wap3@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18570: Drop event trigger for DDL finishes successfully but
 trigger still executed on DDL
Message-ID: <202408061438.eqf4u2oyojau@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <18570-43bc1b85bebd2572@postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/202408061438.eqf4u2oyojau%40alvherre.pgsql>
Precedence: bulk

On 2024-Aug-06, PG Bug reporting form wrote:

> After some time I decided to drop the event trigger. The command is executed
> successfully (DROP EVENT TRIGGER <name> CASCADE) 
> I double checked by querying the information_schema.triggers (the list is
> empty)
> 
> But every time I try to execute a DDL operation, I encounter an error saying
> that DDL function was called.
> The error was saying the operation failed because awsdms_intercept_ddl()
> function. 

Maybe you're dropping the event trigger in one database, but it still
exist in other databases.  For example, if you originally created it in
template1 and it got propagated by CREATE DATABASE into some new one,
then if you drop it from template1 it'll still exist in the databases
you created later.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
¡Ay, ay, ay!  Con lo mucho que yo lo quería (bis)
se fue de mi vera ... se fue para siempre, pa toíta ... pa toíta la vida
¡Ay Camarón! ¡Ay Camarón!                                (Paco de Lucía)