Re: INSERT ... ON CONFLICT DO UPDATE

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: INSERT ... ON CONFLICT DO UPDATE
Date: 2015-07-20 14:07:32
Message-ID: 20150720140732.GP2301@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Geoff Winkless wrote:
> On 20 July 2015 at 14:33, Rafal Pietrak <rafal(at)ztk-rp(dot)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?

Not sure what type of indexes would be affected by that problem, but I
don't think Postgres' btrees would be.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Igor Neyman 2015-07-20 14:56:08 Re: INSERT ... ON CONFLICT DO UPDATE
Previous Message Andres Freund 2015-07-20 14:02:43 Re: Lots of stuck queries after upgrade to 9.4