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.
In response to
pgsql-performance by date
|Next:||From: Merlin Moncure||Date: 2010-09-15 21:10:32|
|Subject: Re: turn off caching for performance test|
|Previous:||From: Greg Smith||Date: 2010-09-15 19:28:24|
|Subject: Re: locking issue on simple selects?|