On Wed, 2007-05-30 at 12:27 -0400, Tom Lane wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > * Tom Lane ([EMAIL PROTECTED]) wrote:
> >> It'd be relatively painless to make that happen as part of the
> >> deadlock-check timeout function, but that's typically only a one-second
> >> delay not a
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > * Tom Lane ([EMAIL PROTECTED]) wrote:
> >> It'd be relatively painless to make that happen as part of the
> >> deadlock-check timeout function, but that's typically only a one-second
> >> delay not a "few seconds"
* Alvaro Herrera ([EMAIL PROTECTED]) wrote:
> Stephen Frost wrote:
> > Yeah, I wouldn't want one per second.
>
> It's not one per second, it's after one second (actually
> deadlock_timeout) has elapsed since you started to sleep waiting for a
> lock. If a deadlock is not detected the process won'
Stephen Frost wrote:
> * Tom Lane ([EMAIL PROTECTED]) wrote:
> > Stephen Frost <[EMAIL PROTECTED]> writes:
> > > It'd be nice to have a NOTICE printed when a wait-on-lock takes longer
> > > than a few seconds.
> >
> > It'd be relatively painless to make that happen as part of the
> > deadlock-
Stephen Frost <[EMAIL PROTECTED]> writes:
> * Tom Lane ([EMAIL PROTECTED]) wrote:
>> It'd be relatively painless to make that happen as part of the
>> deadlock-check timeout function, but that's typically only a one-second
>> delay not a "few seconds". I think it'd likely be overly chatty.
> Yeah
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > It'd be nice to have a NOTICE printed when a wait-on-lock takes longer
> > than a few seconds.
>
> It'd be relatively painless to make that happen as part of the
> deadlock-check timeout function, but that's
Stephen Frost <[EMAIL PROTECTED]> writes:
> It'd be nice to have a NOTICE printed when a wait-on-lock takes longer
> than a few seconds.
It'd be relatively painless to make that happen as part of the
deadlock-check timeout function, but that's typically only a one-second
delay not a "few secon
Greetings,
It'd be nice to have a NOTICE printed when a wait-on-lock takes longer
than a few seconds. It doesn't need to be precise and it doesn't have
to be repeated over and over, just once. Perhaps even controlled by a
GUC, though NOTICEs are generally ignored by non-interactive
app
I guess I could be just unlucky, but I see lots of locks on LWLock 13 in
my trace output for pgbench.
Assuming I count correctly, that is SubtransControlLock.
Why would I be invoking that if I am not issuing a SAVEPOINT ?
Best Regards,
Simon Riggs
---(end of broad
