Re: INSERT ... ON CONFLICT DO UPDATE - Mailing list pgsql-general

From Geoff Winkless
Subject Re: INSERT ... ON CONFLICT DO UPDATE
Date
Msg-id CAEzk6fdwdZvRPQY-pvCGHq_VigM7JkhwvnBa+Je4ZdOhRy8UEw@mail.gmail.com
Whole thread Raw
In response to Re: INSERT ... ON CONFLICT DO UPDATE  (Rafal Pietrak <rafal@ztk-rp.eu>)
Responses Re: INSERT ... ON CONFLICT DO UPDATE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: INSERT ... ON CONFLICT DO UPDATE  (Jeff Janes <jeff.janes@gmail.com>)
Re: INSERT ... ON CONFLICT DO UPDATE  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
On 20 July 2015 at 14:33, Rafal Pietrak <rafal@ztk-rp.eu> wrote:
If I'm not mistaken, the conclusions from posts in this thread are:

3. there are methods (like cryptographic "random" sequence), which
guarantee no conflicts. So one should resort to that.


Some web research suggests that random sequences are not great for indexes because of the resultant "keyspace fragmentation". I'm assuming that means a low number of nodes in the btree leafs, so an increase in memory usage for the index?

Just a thought.

Geoff​

pgsql-general by date:

Previous
From: Spiros Ioannou
Date:
Subject: Re: Lots of stuck queries after upgrade to 9.4
Next
From: Andres Freund
Date:
Subject: Re: Lots of stuck queries after upgrade to 9.4