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-19 00:45:26
Message-ID: CAHOFxGr1TaRSNkgVYschUQ=3X6MBxpvFy17hoaSiTihosUDsbQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Also, have you checked how bloated your indexes are getting? Do you run
default autovacuum settings? Did you update to the new default 2ms cost
delay value? With a destructive queue, it would be very important to ensure
autovacuum is keeping up with the churn. Share your basic table structure
and indexes, sanitized if need be.

>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Laurenz Albe 2020-08-19 06:04:20 Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
Previous Message Michael Lewis 2020-08-19 00:39:45 Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED