Re: Non-overlapping updates blocking each other

From: Seamus Abshere <seamus(at)abshere(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Non-overlapping updates blocking each other
Date: 2017-10-16 15:34:08
Message-ID: 1508168048.1396253.1140453728.5B64B50D@webmail.messagingengine.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Seamus Abshere <seamus(at)abshere(dot)net> writes:
> > * I do have some exotic indexes [2]. gist, gin, postgis, fillfactor...

> On Mon, Oct 16, 2017, at 10:55 AM, Tom Lane wrote:
> I'd bet on the last one, especially since you found that the problem
> was a page-level lock. Did you look to see which relation the page
> lock was in?

The specific relation varies, but it appears to always be compound GIN
index on (jsonb, text)

Can I like decrease the fillfactor or something to make these
"collisions" less frequent?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alex Magnum 2017-10-16 15:39:38 ORDER with CASE and Random for each case
Previous Message Osahon Oduware 2017-10-16 14:54:35 Re: Using Substitution Variables In PostgreSQL