Re: Command Triggers, patch v11 - Mailing list pgsql-hackers

From Thom Brown
Subject Re: Command Triggers, patch v11
Date
Msg-id CAA-aLv5zuJC2RtOPu_=-XOhJFROWLA7P=dtVHgHSdRp5wEzkjQ@mail.gmail.com
Whole thread Raw
In response to Re: Command Triggers, patch v11  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: Command Triggers, patch v11
Re: Command Triggers, patch v11
List pgsql-hackers
On 27 February 2012 19:37, Dimitri Fontaine <dimitri@2ndquadrant.fr> wrote:
> Thom Brown <thom@linux.com> writes:
>> CREATE COMMAND TRIGGER test_cmd_trg
>> BEFORE CREATE SCHEMA,
>>   CREATE OPERATOR,
>>   CREATE COLLATION,
>>   CREATE CAST
>> EXECUTE PROCEDURE my_func();
>>
>> I couldn't drop it completely unless I specified all of those commands.  Why?
>
> Because I couldn't find a nice enough way to implement that given the
> shared infrastructure Robert and Kaigai did put into place to handle
> dropping of objects.  It could be that I didn't look hard enough, I'll
> be happy to get back that feature.

Well the problem is that you can add commands to a trigger en masse,
but you can only remove them one at a time.  Couldn't we at least
allow the removal of multiple commands at the same time?  The docs you
wrote suggest you can do this, but you can't.

--
Thom


pgsql-hackers by date:

Previous
From: Hitoshi Harada
Date:
Subject: Re: Finer Extension dependencies
Next
From: Shigeru Hanada
Date:
Subject: Re: FDW system columns