From: Jerry Sievers <gsievers19@comcast.net>
To: Raj Gandhi <raj01gandhi@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres log configuration for locking
Date: Wed, 03 Dec 2014 15:26:06 -0600
Message-ID: <868uiofms1.fsf@jerry.enova.com> (raw)
In-Reply-To: <CALU_HCOwRjbpbH1yg71nqOV4Fc1HkK6Bj1rdBS2p2hs4gT=EuQ@mail.gmail.com>
References: <CALU_HCOwRjbpbH1yg71nqOV4Fc1HkK6Bj1rdBS2p2hs4gT=EuQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gsievers19@comcast.net, raj01gandhi@gmail.com
Subject: Re: Postgres log configuration for locking
In-Reply-To: <868uiofms1.fsf@jerry.enova.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox