Skip site navigation (1) Skip section navigation (2)

Re: Logging Lock Waits

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Logging Lock Waits
Date: 2007-01-31 00:32:39
Message-ID: 13794.1170203559@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> I'm thinking to write an INFO message, so that people can choose to log
> this and/or the SQL statement if they choose. 
> e.g. INFO: lock wait time of XXX secs has been exceeded

The available timer resources are already overloaded; adding an
independent timeout for this will complicate the code more than seems
justified.  Perhaps you could add a LOG message whenever the
deadlock-check code runs (and doesn't detect an error, so is about to go
back to sleep).  This would take almost no effort, and the granularity
could still be adjusted via the deadlock check timeout.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: David FetterDate: 2007-01-31 03:42:20
Subject: Re: Modifying and solidifying contrib
Previous:From: Tom LaneDate: 2007-01-31 00:10:28
Subject: Re: parsenodes vs. primnodes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group