From: Bill Moran <wmoran@collaborativefusion.com>
To: Sachchida Ojha <sojha@secure-elements.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: deadlock_timeout parameter in Postgresql.cof
Date: Thu, 23 Aug 2007 14:52:08 -0400
Message-ID: <20070823145208.968faeb9.wmoran@collaborativefusion.com> (raw)
In-Reply-To: <E099DB9EF394534CBA0F62ED03CF3BBF06077E9E@EXVS01.IceMAIL.com>
References: <E099DB9EF394534CBA0F62ED03CF3BBF06077E9E@EXVS01.IceMAIL.com>
In response to "Sachchida Ojha" <sojha@secure-elements.com>:
> I am having some dead locking problem with my app system. Our dev are
> debugging the app to find out the cause of the problem. In the mean time
> I looked at postgresql.conf file. I found that there is a parameter in
> postgresql.conf file deadlock_timeout which was set 1000 (ms). Normally
> I see deadlock in the night or when auto vacuum is running for a long
> time.
>
> My question is
>
> What is the significance of this parameter and updating this parameter
> value will make any difference ?
Does the documentation leave anything unanswered?
http://www.postgresql.org/docs/8.2/static/runtime-config-locks.html
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
wmoran@collaborativefusion.com
Phone: 412-422-3463x4023
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: wmoran@collaborativefusion.com, sojha@secure-elements.com
Subject: Re: deadlock_timeout parameter in Postgresql.cof
In-Reply-To: <20070823145208.968faeb9.wmoran@collaborativefusion.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox