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

From Peter Eisentraut
Subject Re: Detail part for still waiting for lock log message
Date
Msg-id 1377356323.8206.8.camel@vanquo.pezone.net
Whole thread Raw
In response to Detail part for still waiting for lock log message  (Tarvi Pillessaar <tarvip@gmail.com>)
Responses Re: Detail part for still waiting for lock log message  (Tarvi Pillessaar <tarvip@gmail.com>)
List pgsql-hackers
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]





pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: UNNEST with multiple args, and TABLE with multiple funcs
Next
From: Peter Eisentraut
Date:
Subject: Re: Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls