Re: deadlock_timeout parameter in Postgresql.cof

From: Bill Moran <wmoran(at)collaborativefusion(dot)com>
To: "Sachchida Ojha" <sojha(at)secure-elements(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: deadlock_timeout parameter in Postgresql.cof
Date: 2007-08-23 18:52:08
Message-ID: 20070823145208.968faeb9.wmoran@collaborativefusion.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

In response to "Sachchida Ojha" <sojha(at)secure-elements(dot)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(at)collaborativefusion(dot)com
Phone: 412-422-3463x4023

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2007-08-23 18:56:19 Re: long-running query - needs tuning
Previous Message Sachchida Ojha 2007-08-23 18:23:57 deadlock_timeout parameter in Postgresql.cof