Re: Locks Postgres

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Locks Postgres
Date: 2017-02-10 05:16:55
Message-ID: 62f1ee81-c2ee-b5fd-d521-bc5ba763916f@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/9/2017 9:00 PM, Patrick B wrote:
>
> Access share = Does that mean queries were waiting because an
> update/delete/insert was happening?
>

access share is taken by a SELECT, and all it blocks is an ACCESS
EXCLUSIVE lock, which is taken by operations like ALTER TABLE, VACUUM
FULL, and such global table operations. that spike in your graph
suggests you had 8000 concurrent SELECT operations going on, which is
likely way more than you have compute and IO resources to handle
efficiently.

--
john r pierce, recycling bits in santa cruz

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2017-02-10 05:18:30 Re: Locks Postgres
Previous Message Adrian Klaver 2017-02-10 05:06:05 Re: Locks Postgres