Re: Postgres log configuration for locking - Mailing list pgsql-admin

From Jerry Sievers
Subject Re: Postgres log configuration for locking
Date
Msg-id 868uiofms1.fsf@jerry.enova.com
Whole thread Raw
In response to Postgres log configuration for locking  (Raj Gandhi <raj01gandhi@gmail.com>)
List pgsql-admin
Raj Gandhi <raj01gandhi@gmail.com> writes:

> I’m using Postgres 9.1 and enabled the log configuration param ‘log_lock_waits’.
>  
> However, it only logs the session which is waiting for the lock longer than ‘deadlock_timeout’. It doesn’t log
thesession which acquired the lock?  
>  
> Is there a way to log the session that acquired the lock along with the session which is waiting for the lock?

Do you assume there is but 1 single session blocking the waiter?

False in cases where some N number of sessions are all holding less
invasive locks and you are pending on a heavier one.

To wit; share locks granted and an exclusive locker pending.

The question in regards to whether it's possible to  log more info
here in any case  isn't something I can answer personally.

HTH


>  
> Thanks,
> Raj
>
>  
>

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 312.241.7800


pgsql-admin by date:

Previous
From: Raj Gandhi
Date:
Subject: Postgres log configuration for locking
Next
From: Khangelani Gama
Date:
Subject: Postgres 9.2.4 : psql: symbol lookup error: psql: undefined symbol: PQconnectdbParams