Re: delta relations in AFTER triggers

From: Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Khandekar <amit(dot)khandekar(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: delta relations in AFTER triggers
Date: 2016-12-18 02:29:51
Message-ID: CAMsr+YGVbC2_ThxSG5LduE6x+EVUkEba_exSyDSRZKqhbFao2A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22 Nov. 2016 03:01, "Thomas Munro" <thomas(dot)munro(at)enterprisedb(dot)com> wrote:

How about a QueryEnvironment (as shown in the
patch I posted) that contains a list of NamedTuplestore pointers (the
SpiRelation struct in the patch I posted, renamed) and in future
perhaps lists of other ephemeral/transient objects that we want to
expose to SQL?

Very good idea. Sooner or later someone will probably want query-scoped
variables like MS-SQL and MySQL for example.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2016-12-18 10:12:22 Re: Logical Replication WIP
Previous Message Craig Ringer 2016-12-18 02:25:34 Re: delta relations in AFTER triggers