On Jan 30, 2007, at 6:32 PM, Tom Lane wrote:
"Simon Riggs" <[EMAIL PROTECTED]> 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 a
"Simon Riggs" <[EMAIL PROTECTED]> 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
Right now, I need a way to log the lock wait times for certain queries,
to see if they are acceptable. DTrace is not available.
I'm dealing with a problem that is either a standard lock wait involving
RI trigger locking, or a weirder problem involving lock starvation as a
result of soft deadlock q
