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

From Robert Haas
Subject Re: Command Triggers, patch v11
Date
Msg-id CA+TgmoZkgpzFkw2odrog1r6x2Wwqwk+mQizbFR6zoQbTk6BArQ@mail.gmail.com
Whole thread Raw
In response to Re: Command Triggers, patch v11  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Command Triggers, patch v11  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Tue, Feb 28, 2012 at 10:09 AM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> This seems over-complicated.  Triggers on tables do not have
>> alterable properties, why should command triggers?  I vote for
>>
>>       CREATE COMMAND TRIGGER name ... properties ...;
>>
>>       DROP COMMAND TRIGGER name;
>>
>> full stop.  If you want to run the same trigger function on some
>> more commands, add another trigger name.
>
> +1

+1.  I suggested the same thing a while back.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Re: Command Triggers, patch v11
Next
From: "anarazel@anarazel.de"
Date:
Subject: Re: Command Triggers, patch v11