Re: Patch: Show process IDs of processes holding a lock; show relation and tuple infos of a lock to acquire - Mailing list pgsql-hackers

From Christian Kruse
Subject Re: Patch: Show process IDs of processes holding a lock; show relation and tuple infos of a lock to acquire
Date
Msg-id 20140128080835.GB26938@defunct.ch
Whole thread Raw
In response to Re: Patch: Show process IDs of processes holding a lock; show relation and tuple infos of a lock to acquire  (Rajeev rastogi <rajeev.rastogi@huawei.com>)
Responses Re: Patch: Show process IDs of processes holding a lock; show relation and tuple infos of a lock to acquire  (Rajeev rastogi <rajeev.rastogi@huawei.com>)
List pgsql-hackers
Hi,

On 27/01/14 11:44, Rajeev rastogi wrote:
> I have checked the revised patch. It looks fine to me except one minor code formatting issue.
> In elog.c, two tabs are missing in the definition of function "errdetail_log_plural".
> Please run pgindent tool to check the same.

I did, but this reformats various other locations in the file,
too. Nevertheless I now ran pg_indent against it and removed the other
parts. Attached you will find the corrected patch version.

> Also I would like to highlight one behavior here is that process ID of process trying to
> acquire lock is also listed in the list of "Request queue". E.g.
>
>       session 1 with process id X: BEGIN; LOCK TABLE foo IN SHARE MODE;
>       session 2 with process id Y: BEGIN; LOCK TABLE foo IN EXCLUSIVE MODE;
>
> On execution of LOCK in session-2, as part of log it will display as:
>       DETAIL:  Process holding the lock: X. Request queue: Y.
>
>       Where Y is the process ID of same process, which was trying to acquire lock.

This is on purpose due to the rewording of the Message. In the first
version the PID of the backend was missing.

Thanks for the review!

Best regards,

--
 Christian Kruse               http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


Attachment

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: GIN improvements part2: fast scan
Next
From: Yugo Nagata
Date:
Subject: Re: Fwd: Proposal: variant of regclass