Horton

Re: Transition tables vs ON CONFLICT

Thomas Munro <thomas.munro@enterprisedb.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@enterprisedb.com>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>
Cc: Kevin Grittner <kgrittn@gmail.com>, Peter Geoghegan <pg@bowt.ie>, Craig Ringer <craig@2ndquadrant.com>, Marko Tiikkaja <marko@joh.to>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-06-12T19:19:00Z
Lists: pgsql-hackers

Attachments

On Mon, Jun 12, 2017 at 2:40 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> On Fri, Jun 9, 2017 at 4:10 PM, Thomas Munro
> <thomas.munro@enterprisedb.com> wrote:
>> On Wed, Jun 7, 2017 at 10:47 AM, Peter Geoghegan <pg@bowt.ie> wrote:
>>> I suppose you'll need two tuplestores for the ON CONFLICT DO UPDATE
>>> case -- one for updated tuples, and the other for inserted tuples.
>>
>> [...]
>>
>> Here is a patch implementing the above.  It should be applied on top
>> of transition-tuples-from-wctes-v2.patch[2].
>
> Here's a new version of patch #3.

That accidentally removed a comment that I wanted to keep.  Here is a
better version.

-- 
Thomas Munro
http://www.enterprisedb.com

Commits

  1. Fix transition tables for ON CONFLICT.