From: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: locking issue on simple selects? |
Date: | 2010-09-15 19:32:56 |
Message-ID: | 4C911F68.6020507@ca.afilias.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 10-09-15 03:07 PM, Tobias Brox wrote:
> On 15 September 2010 15:39, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> An exclusive lock will block selects too. Have you looked into pg_locks
>> for ungranted lock requests?
> Well - I thought so, we have a logging script that logs the content of
> the pg_locks table, it didn't log anything interesting but it may be a
> problem with the script itself. It does an inner join on
> pg_locks.relation = pg_class.oid but when I check now this join seems
> to remove most of the rows in the pg_locks table. Does it make sense
> at all to join pg_class with pg_locks? I will ask the sysadm to
> change to an outer join as for now.
>
You can also enable log_lock_waits and the lock waits will appear in
your Postgres logs.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2010-09-15 21:10:32 | Re: turn off caching for performance test |
Previous Message | Greg Smith | 2010-09-15 19:28:24 | Re: locking issue on simple selects? |