Re: delta relations in AFTER triggers

Kevin Grittner <kgrittn@ymail.com>

From: Kevin Grittner <kgrittn@ymail.com>

To: David Fetter <david@fetter.org>

Cc: Robert Haas <robertmhaas@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2014-06-30T16:22:21Z

Lists: pgsql-hackers

Attachments

transition-table-c-v2.diff (text/x-diff) patch v2

David Fetter <david@fetter.org> wrote:

> It's missing a few pieces like surfacing transition table names. 
> I'll work on those.  Also, it's not clear to me how to access the
> pre- and post- relations at the same time, this being necessary
> for many use cases.  I guess I need to think more about how that
> would be done.

If you're going to do any work on the C extension, please start
from the attached.  I renamed it to something which seemed more
meaningful (to me, at least), and cleaned up some cosmetic issues. 
The substance is the same.

--
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