Re: [GENERAL] Locks Postgres - Mailing list pgsql-general

From John R Pierce
Subject Re: [GENERAL] Locks Postgres
Date
Msg-id 62f1ee81-c2ee-b5fd-d521-bc5ba763916f@hogranch.com
Whole thread Raw
In response to [GENERAL] Locks Postgres  (Patrick B <patrickbakerbr@gmail.com>)
Responses Re: [GENERAL] Locks Postgres  (John R Pierce <pierce@hogranch.com>)
List 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



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: [GENERAL] Locks Postgres
Next
From: John R Pierce
Date:
Subject: Re: [GENERAL] Locks Postgres