Re: Detail part for still waiting for lock log message - Mailing list pgsql-hackers

From Tarvi Pillessaar
Subject Re: Detail part for still waiting for lock log message
Date
Msg-id 521B479A.2020502@gmail.com
Whole thread Raw
In response to Re: Detail part for still waiting for lock log message  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Detail part for still waiting for lock log message  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Fixed patch attached.

Regards,
Tarvi Pillessaar

On 24.08.2013 17:58, Peter Eisentraut wrote:
> On Tue, 2013-08-20 at 19:21 +0300, Tarvi Pillessaar wrote:
>> About patch:
>> Patch is tested against 9.2.4.
>> I was not sure that i should check if the lock holder's proclock was
>> found (as lock holder's proclock should be always there), check is there
>> to be on the safe side, but maybe it's unnecessary.
>> If it's not needed then fallback to old behavior (logging without
>> detail) is not needed as well.
>> And yes, i know that the lock holding time is not actually correct and
>> it actually shows milliseconds since transaction start.
>>
> Please fix this compiler warning:
>
> proc.c: In function ‘ProcSleep’:
> proc.c:1258:6: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
>
>


Attachment

pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Backup throttling
Next
From: Oleg Bartunov
Date:
Subject: Re: Hstore: Query speedups with Gin index