On Sat, Sep 13, 2008 at 09:04:08PM +0200, Cyril SCETBON wrote:

> Bad news :-( It would really be great to have such an option. as DROP 
> trigger is a DDL statement it can't be done in a transaction (afaik) 
> without disturbing other transactions, so maybe another way could to start 
> a transaction, updating a field (disable_trigger_work=1) in a table, doing 
> all the DML, setting the field to the origin value 
> ((disable_trigger_work=0) and ending the transaction. But this way, it adds 
> a select for every trigger call. It can be a starting point

No, none of this will work.  It's always going to block all other
transactions on the origin.  BTW, DDL _can_ be done in a transaction
on Postgres.  It's one of the coolest Postgres features.

A

-- 
Andrew Sullivan
ajs at commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/