[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] Logging Lock Waits
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2007-01-31 0:32:39
Message-ID: 13794.1170203559 () sss ! pgh ! pa ! us
[Download RAW message or body]

"Simon Riggs" <simon@2ndquadrant.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

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org
[prev in list] [next in list] [prev in thread] [next in thread]