Re: Command Triggers, patch v11
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: pgsql-hackers@postgresql.org
Cc: Dimitri Fontaine <dimitri@2ndquadrant.fr>, Thom Brown <thom@linux.com>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2012-03-05T21:10:37Z
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
On Monday, March 05, 2012 09:42:00 PM Dimitri Fontaine wrote: > > Still no command triggers firing for CREATE TABLE AS: > Yes, Andres made CTAS a utility command, he didn't add the code that > make them fire command triggers. I would expect his patch to get in > first, so I don't expect him to be adding that support, I think I will > have to add it when rebasing once his patch has landed. That was my assumption as well. Any opinions about adding the patch to the commitfest other than from dim? I feel a bit bad adding it to the in-progress one even if its belongs there because is a part of the command trigger stuff... Andres