Re: Unexpected behavior with transition tables in update statement trigger

Tom Kazimiers <tom@voodoo-arts.net>

From: Tom Kazimiers <tom@voodoo-arts.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>, Pg Hackers <pgsql-hackers@postgresql.org>, PG-General Mailing List <pgsql-general@postgresql.org>
Date: 2018-02-27T21:40:32Z
Lists: pgsql-hackers, pgsql-general
On Tue, Feb 27, 2018 at 03:58:14PM -0500, Tom Lane wrote:
>Thomas Munro <thomas.munro@enterprisedb.com> writes:
>> Here's a new version with tuplestore_select_read_pointer() added in
>> another place where it was lacking, and commit message.  Moving to
>> -hackers, where patches go.
>
>Pushed, along with a regression test based on your example.
>Unfortunately, this came in a bit too late for this week's releases :-(

Ah, so close. :-) Regardless, thanks both of you for fixing this and 
committing the fix to master. I am looking forward to the release 
including this.

Cheers,
Tom


Commits

  1. Use the correct tuplestore read pointer in a NamedTuplestoreScan.