[HACKERS] Detail part for still waiting for lock log message

2013-08-20 Thread Tarvi Pillessaar
time is not actually correct and it actually shows milliseconds since transaction start. Regards, Tarvi Pillessaar diff --git a/src/backend/storage/lmgr/proc.c b/src/backend/storage/lmgr/proc.c index 3bfdd23..4dc7b37 100644 --- a/src/backend/storage/lmgr/proc.c +++ b/src/backend/storage/lmgr

Re: [HACKERS] Detail part for still waiting for lock log message

2013-08-26 Thread Tarvi Pillessaar
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

Re: [HACKERS] Detail part for still waiting for lock log message

2013-08-27 Thread Tarvi Pillessaar
with the lock) before the report has completed? If this happens, is there a problem? That's why i have added check if other backend is found etc, but maybe i missed something. This is one of reasons why i wanted feedback. Regards Tarvi Pillessaar -- Sent via pgsql-hackers mailing list (pgsql-hackers