From: Jerry Sievers <gsievers19@comcast.net>
To: Raj Gandhi <raj01gandhi@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres log configuration for locking
References: 
 <CALU_HCOwRjbpbH1yg71nqOV4Fc1HkK6Bj1rdBS2p2hs4gT=EuQ@mail.gmail.com>
Date: Wed, 03 Dec 2014 15:26:06 -0600
In-Reply-To: 
 <CALU_HCOwRjbpbH1yg71nqOV4Fc1HkK6Bj1rdBS2p2hs4gT=EuQ@mail.gmail.com>
 (Raj Gandhi's message of "Wed, 3 Dec 2014 15:07:12 -0500")
Message-ID: <868uiofms1.fsf@jerry.enova.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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 the session 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


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin