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

Re: 'Waiting on lock'

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 'Waiting on lock'
Date: 2007-05-30 16:33:45
Message-ID: 20070530163345.GE7128@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Stephen Frost wrote:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> > Stephen Frost <sfrost(at)snowman(dot)net> 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 seconds".  I think it'd likely be overly chatty.
> 
> 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't be awakened
again.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2007-05-30 16:43:58
Subject: Re: TOAST usage setting
Previous:From: Tom LaneDate: 2007-05-30 16:27:22
Subject: Re: 'Waiting on lock'

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