Re: Command Triggers, patch v11

Dimitri Fontaine <dimitri@2ndquadrant.fr>

From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>, Thom Brown <thom@linux.com>, Tom Lane <tgl@sss.pgh.pa.us>, Dimitri Fontaine <dimitri@2ndquadrant.fr>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2012-03-03T13:45:10Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix SPGiST vacuum algorithm to handle concurrent tuple motion properly.
- b4af1c25bbc6 9.2.0 cited
Remove useless const qualifier
- 66f0cf7da8ee 9.2.0 cited
Make executor's SELECT INTO code save and restore original tuple receiver.
- dfd26f9c5f37 9.2.0 cited

Robert Haas <robertmhaas@gmail.com> writes:
>>>       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.

Yeah, I know, I just wanted to hear from more people before ditching out
a part of the work I did, and Thom was balancing in the opposite
direction.

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support