On Thu, Sep 25, 2014 at 7:12 AM, Simon Riggs <si...@2ndquadrant.com> wrote: > The way forwards, in my view, is to define precisely the behaviour we > wish to have. That definition will include the best current mechanism > for running an UPSERT using INSERT/UPDATE/loops and comparing that > against what is being provided here. We will then have a functional > test of equivalence of the approaches, and a basis for making a > performance test that shows that performance is increased without any > loss of concurrency.
That sounds very reasonable. While I'm sure that what I have here can decisively beat the xact looping pattern in terms of performance as measured by pgbench, the real performance advantage is that this approach doesn't burn through XIDs. That was a concern that Andres highlighted in relation to using the subxact looping pattern with BDR's multi-master replication conflict resolution. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
