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 13:32:09 |
Message-ID: | CAA-aLv7=nSyhv90QVBgD-3Ut8y5DocY6MiKD6hSfvhdWSqcKfw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28 February 2012 11:43, Thom Brown <thom(at)linux(dot)com> wrote:
> 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.
Also note that as of commit 66f0cf7da8eeaeca4b9894bfafd61789b514af4a
(Remove useless const qualifier) the patch no longer applies due to
changes to src/backend/commands/typecmds.c.
--
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-02-28 14:35:06 | Re: FDW system columns |
Previous Message | Shigeru Hanada | 2012-02-28 12:00:18 | Re: FDW system columns |