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

From Tom Lane
Subject Re: Unexpected behavior with transition tables in update statement trigger
Date
Msg-id 24943.1519765094@sss.pgh.pa.us
Whole thread Raw
In response to Re: Unexpected behavior with transition tables in update statement trigger  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: Unexpected behavior with transition tables in update statement trigger  (Thomas Munro <thomas.munro@enterprisedb.com>)
Re: Unexpected behavior with transition tables in update statement trigger  (Thomas Munro <thomas.munro@enterprisedb.com>)
Re: Unexpected behavior with transition tables in update statementtrigger  (Tom Kazimiers <tom@voodoo-arts.net>)
Re: Unexpected behavior with transition tables in update statementtrigger  (Tom Kazimiers <tom@voodoo-arts.net>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: PATCH: Configurable file mode mask
Next
From: Thomas Munro
Date:
Subject: Re: Registering LWTRANCHE_PARALLEL_HASH_JOIN