Re: Command Triggers, patch v11

Alvaro Herrera <alvherre@commandprompt.com>

From: Alvaro Herrera <alvherre@commandprompt.com>

To: Andres Freund <andres@anarazel.de>

Cc: Pg Hackers <pgsql-hackers@postgresql.org>, Dimitri Fontaine <dimitri@2ndquadrant.fr>

Date: 2012-03-13T15:14:06Z

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

Excerpts from Andres Freund's message of mar mar 13 08:22:26 -0300 2012:

> - I think list_command_triggers should do a heap_lock_tuple(LockTupleShared)
>  on the command trigger tuple. But then again just about nothing else does :(

If you want to do something like that, I think it's probably more
appropriate to use LockDatabaseObject than heap_lock_tuple.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support