Re: Unexpected behavior with transition tables in update statementtrigger - Mailing list pgsql-hackers

From Tom Kazimiers
Subject Re: Unexpected behavior with transition tables in update statementtrigger
Date
Msg-id 20180227214032.ogxicajyh3pngaq6@dewberry.localdomain
Whole thread Raw
In response to Re: Unexpected behavior with transition tables in update statement trigger  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Unexpected behavior with transition tables in update statement trigger
Next
From: Nikita Glukhov
Date:
Subject: [PATCH] Opclass parameters