Horton

Re: Unexpected behavior with transition tables in update statement trigger

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Tom Kazimiers <tom@voodoo-arts.net>, Pg Hackers <pgsql-hackers@postgresql.org>, PG-General Mailing List <pgsql-general@postgresql.org>
Date: 2018-02-27T20:58:14Z
Lists: pgsql-hackers, pgsql-general 
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 :-(

			regards, tom lane

Commits

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