| From: | Tom Kazimiers <tom(at)voodoo-arts(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, 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 21:40:32 |
| Message-ID: | 20180227214032.ogxicajyh3pngaq6@dewberry.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, Feb 27, 2018 at 03:58:14PM -0500, Tom Lane wrote:
>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 :-(
Ah, so close. :-) Regardless, thanks both of you for fixing this and
committing the fix to master. I am looking forward to the release
including this.
Cheers,
Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-27 21:58:11 | Re: index-only-scan when there is an index on all columns |
| Previous Message | Thomas Munro | 2018-02-27 21:27:23 | Re: Unexpected behavior with transition tables in update statement trigger |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikita Glukhov | 2018-02-27 21:46:36 | [PATCH] Opclass parameters |
| Previous Message | Thomas Munro | 2018-02-27 21:27:23 | Re: Unexpected behavior with transition tables in update statement trigger |