On Fri, Jun 9, 2017 at 4:10 PM, Thomas Munro <thomas.mu...@enterprisedb.com> wrote: > On Wed, Jun 7, 2017 at 10:47 AM, Peter Geoghegan <p...@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. 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
