Re: Unexpected behavior with transition tables in update statement trigger

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 *

Re: Unexpected behavior with transition tables in update statement trigger

On Tue, Feb 27, 2018 at 03:58:14PM -0500, Tom Lane wrote: Thomas Munro 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

Re: Unexpected behavior with transition tables in update statement trigger

On Tue, Feb 27, 2018 at 02:52:02PM +1300, Thomas Munro wrote: On Tue, Feb 27, 2018 at 4:18 AM, Tom Kazimiers <t...@voodoo-arts.net> wrote: It would be great if this or a similar fix would make it into the next official release. Here's a new version with tuplestore_select_read_pointer()