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 ?



Thanks

Regards

sachi

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/s...fig-locks.html

--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran@collaborativefusion.com
Phone: 412-422-3463x4023

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match