Re: [HACKERS] Transition tables vs ON CONFLICT
On Mon, Jun 19, 2017 at 11:04 AM, Andrew Gierthwrote: >> "Thomas" == Thomas Munro writes: > > Thomas> That accidentally removed a comment that I wanted to keep. > Thomas> Here is a better version. > > I plan to commit this soon; if anyone has any comment to make, now would > be a good time. Here's patch #3 rebased for the recent reindent. -- Thomas Munro http://www.enterprisedb.com transition-tuples-from-on-conflict-v4.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Transition tables vs ON CONFLICT
> "Thomas" == Thomas Munrowrites: Thomas> That accidentally removed a comment that I wanted to keep. Thomas> Here is a better version. I plan to commit this soon; if anyone has any comment to make, now would be a good time. -- Andrew (irc:RhodiumToad) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Transition tables vs ON CONFLICT
On Mon, Jun 12, 2017 at 2:40 PM, Thomas Munrowrote: > On Fri, Jun 9, 2017 at 4:10 PM, Thomas Munro > wrote: >> On Wed, Jun 7, 2017 at 10:47 AM, Peter Geoghegan 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 transition-tuples-from-on-conflict-v3.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Transition tables vs ON CONFLICT
On Fri, Jun 9, 2017 at 4:10 PM, Thomas Munrowrote: > On Wed, Jun 7, 2017 at 10:47 AM, Peter Geoghegan 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. It's rebased on top of transition-tuples-from-wctes-v3.patch. I also moved a comment for execReplication.c out of this patch into patch #2, correcting a mistake in my pancake stacking. -- Thomas Munro http://www.enterprisedb.com transition-tuples-from-on-conflict-v2.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers