Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Jim Jarvie <jim(at)talentstack(dot)to>
Cc: Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
Date: 2020-08-20 21:42:36
Message-ID: CAHOFxGp_r5=TLNJX7insLP=L=o24tojKnopRo9fvzKPFxJi8Ww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Can you share an explain analyze for the query that does the select for
update? I wouldn't assume that partition pruning is possible at all with
hash, and it would be interesting to see how it is finding those rows.

>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jim Jarvie 2020-08-20 22:39:59 Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
Previous Message Jim Jarvie 2020-08-20 21:13:27 Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED