Re: Unexpected behavior with transition tables in update statement trigger

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Tom Kazimiers <tom(at)voodoo-arts(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unexpected behavior with transition tables in update statement trigger
Date: 2018-02-27 20:58:14
Message-ID: 24943.1519765094@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2018-02-27 21:08:04 Re: index-only-scan when there is an index on all columns
Previous Message Hadi Moshayedi 2018-02-27 20:49:17 index-only-scan when there is an index on all columns

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-02-27 20:58:25 Re: Registering LWTRANCHE_PARALLEL_HASH_JOIN
Previous Message David Steele 2018-02-27 20:52:32 Re: PATCH: Configurable file mode mask