Horton

Re: Unexpected behavior with transition tables in update statement trigger

Tom Kazimiers <tom@voodoo-arts.net>

View thread View on postgr.es
From: Tom Kazimiers <tom@voodoo-arts.net>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Pg Hackers <pgsql-hackers@postgresql.org>, PG-General Mailing List <pgsql-general@postgresql.org>
Date: 2018-02-27T22:54:44Z
Lists: pgsql-hackers, pgsql-general 
On Wed, Feb 28, 2018 at 10:27:23AM +1300, Thomas Munro wrote:
>Tom K, if you need a workaround before 10.4 comes out in May[1], you
>could try selecting the whole transition table into a CTE up front.
>Something like WITH my_copy AS (SELECT * FROM new_table) SELECT * FROM
>my_copy UNION ALL SELECT * FROM my_copy should work.
>
>[1] https://www.postgresql.org/developer/roadmap/

Thanks, that's what I am going to do.

Cheers,
Tom

Commits

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