Re: Update blocking a select count(*)?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Benedict Holland" <benedict(dot)m(dot)holland(at)gmail(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Update blocking a select count(*)?
Date: 2012-06-15 18:43:30
Message-ID: 4FDB3C0202000025000484E4@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
> Benedict Holland <benedict(dot)m(dot)holland(at)gmail(dot)com> wrote:
>> Do I seem to have this right and is there anything I can do?
>
> There are a couple of maintenance operations that could block a
> select. Do you see any AccessExclusive locks within pg_locks?
> That's the only type of lock that will block a select statement's
> AccessShare lock.

To check for that, see the queries on these Wiki pages:

http://wiki.postgresql.org/wiki/Lock_Monitoring
http://wiki.postgresql.org/wiki/Lock_dependency_information

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Benedict Holland 2012-06-15 18:46:09 Re: Update blocking a select count(*)?
Previous Message Kevin Grittner 2012-06-15 18:41:02 Re: Update blocking a select count(*)?