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

Re: BUG #2466: lock issues...

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2466: lock issues...
Date: 2006-06-05 10:16:46
Message-ID: e610an$263h$ (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
""P.P.S. Narayan"" <ppsnarayan(at)lucent(dot)com> wrote
> However, there are a bunch of http requests that come in after the hanging
> request, which get deadlocked on the locks held by the hanging request. AS
> far as I have read, there is a lock_timeout parameter in postgresql config
> file to timeout after 1s. But none of the latter http requests timeout.

There is a deadlock_timeout parameter in the configure file, which is "the
time in milliseconds to wait on lock before checking for deadlock." If a
deadlock is resolved, you will see an error message like "deadlock detected"
with some details. Also, you can see current lock status via pg_locks view
to see "information about the locks held by open transactions within the
database server". More details can be found in the docs.


In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-06-05 15:46:29
Subject: Re: BUG #2467: Documentation
Previous:From: Serkan EksiDate: 2006-06-05 09:50:10
Subject: BUG #2470: Field DefVal And Description

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