Re: PG10 transition tables, wCTEs and multiple operations on the same table

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG10 transition tables, wCTEs and multiple operations on the same table
Date: 2017-06-07 00:01:11
Message-ID: CAH2-Wz=k__9sVGf=0aozdtEUeehOWvcSZZN4FS2J9A1ewNyC3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 6, 2017 at 3:47 PM, Peter Geoghegan <pg(at)bowt(dot)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.

Also, ISTM that the code within ENRMetadataGetTupDesc() probably
requires more explanation, resource management wise.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2017-06-07 00:04:25 Re: GSoC 2017 : Proposal for predicate locking in gist index
Previous Message Kevin Grittner 2017-06-06 23:40:27 Re: GSoC 2017 weekly progress reports ("Explicitly support predicate locks in index access methods besides b-tree")