Horton

Re: delta relations in AFTER triggers

Craig Ringer <craig.ringer@2ndquadrant.com>

View thread View on postgr.es
From: Craig Ringer <craig.ringer@2ndquadrant.com>
To: Kevin Grittner <kgrittn@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Álvaro Herrera <alvherre@2ndquadrant.com>, Amit Khandekar <amit.khandekar@enterprisedb.com>, Thomas Munro <thomas.munro@enterprisedb.com>, Kevin Grittner <kgrittn@ymail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael.paquier@gmail.com>, Heikki Linnakangas <hlinnakangas@vmware.com>, David Fetter <david@fetter.org>, Robert Haas <robertmhaas@gmail.com>
Date: 2016-12-18T02:25:34Z
Lists: pgsql-hackers 
On 22 Nov. 2016 01:05, "Kevin Grittner" <kgrittn@gmail.com> wrote:



Right, I think we should assume that there will be other ways
people want to use parts of what is done here, including building
tuplestores through other means and referencing them in queries.


Yes. PL/pgsql table-valued variables for one thing.

Commits

  1. Don't permit transition tables with TRUNCATE triggers.

  2. Pass EXEC_FLAG_REWIND when initializing a tuplestore scan.

  3. Faster expression evaluation and targetlist projection.

  4. Remove obsoleted code relating to targetlist SRF evaluation.

  5. Implement syntax for transition tables in AFTER triggers.