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 20180227225444.haimi5j2equ5fzeg@dewberry.localdomain
Whole thread Raw
In response to Re: Unexpected behavior with transition tables in update statement trigger  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Reopen logfile on SIGHUP
Next
From: Tom Lane
Date:
Subject: Re: Reopen logfile on SIGHUP