Re: delta relations in AFTER triggers
Kevin Grittner <kgrittn@ymail.com>
From: Kevin Grittner <kgrittn@ymail.com>
To: Robert Haas <robertmhaas@gmail.com>, David Fetter <david@fetter.org>,
Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2014-06-19T15:57:18Z
Lists: pgsql-hackers
Kevin Grittner <kgrittn@ymail.com> wrote: > I've already said that I now think we should use the standard > CREATE TRIGGER syntax to specify the transition tables, and that > if we do that we don't need the reloption that's in the patch. > If you ignore the 19 lines of new code to add that reloption, > absolutely 100% of the code changes in the patch so far are in > trigger.c and trigger.h. Although nobody has actually framed their feedback as a review, I feel that I have enough to work with to throw the patch into Waiting on Author status. Since I started with the assumption that I was going to be using standard syntax and got a ways into that before convincing myself it was a bad idea, I should have a new version of the patch working that way in a couple days. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Don't permit transition tables with TRUNCATE triggers.
- 29fd3d9da0ff 10.0 landed
-
Pass EXEC_FLAG_REWIND when initializing a tuplestore scan.
- 304007d9f1f6 10.0 landed
-
Faster expression evaluation and targetlist projection.
- b8d7f053c5c2 10.0 cited
-
Remove obsoleted code relating to targetlist SRF evaluation.
- ea15e18677fc 10.0 cited
-
Implement syntax for transition tables in AFTER triggers.
- 8c48375e5f43 10.0 cited