From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Command Triggers, patch v11 |
Date: | 2012-02-28 11:43:54 |
Message-ID: | CAA-aLv5zuJC2RtOPu_=-XOhJFROWLA7P=dtVHgHSdRp5wEzkjQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 27 February 2012 19:37, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> wrote:
> Thom Brown <thom(at)linux(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Shigeru Hanada | 2012-02-28 12:00:18 | Re: FDW system columns |
Previous Message | Hitoshi Harada | 2012-02-28 10:34:59 | Re: Finer Extension dependencies |