Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] PG10 transition tables, wCTEs and multiple operationson the same table - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [HACKERS] PG10 transition tables, wCTEs and multiple operationson the same table
Date
Msg-id CAH2-Wzn-hhxE0Ljpkn=Gc=juP-CN0zawuT3nQNm6H14vHJRDQA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] PG10 transition tables, wCTEs and multiple operationson the same table  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: [HACKERS] PG10 transition tables, wCTEs and multiple operationson the same table
Re: [HACKERS] PG10 transition tables, wCTEs and multiple operationson the same table
List pgsql-hackers
Tree view 
On Mon, Jun 5, 2017 at 6:40 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> After sleeping on it, I don't think we need to make that decision here
> though.  I think it's better to just move the tuplestores into
> ModifyTableState so that each embedded DML statement has its own, and
> have ModifyTable pass them to the trigger code explicitly.

I suppose you'll need two tuplestores for the ON CONFLICT DO UPDATE
case -- one for updated tuples, and the other for inserted tuples.


-- 
Peter Geoghegan

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] libpqrcv_PQexec() seems to violate latch protocol
Next
From: "Jim Van Fleet"
Date:
Subject: Re: [HACKERS] HACKERS[PROPOSAL] split ProcArrayLock into multiple parts