deadlock_timeout and pg_ctl reload - Mailing list pgsql-bugs

From A.Bhuvaneswaran
Subject deadlock_timeout and pg_ctl reload
Date
Msg-id Pine.LNX.4.44.0307211249480.10445-100000@Bhuvan.bksys.co.in
Whole thread Raw
Responses Re: deadlock_timeout and pg_ctl reload  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
List pgsql-bugs
Hi,

I am using pgsql 7.3.2.

If we change the deadlock_timeout value in postgresql.conf and say pg_ctl
reload, the new value is not taken affect. But any other changes like,
datestyle, log_connection, log_pid, etc are taken affect immediately when
we say pg_ctl reload. When we restart the server, the changed
deadlock_timeout value is taken affect.

Example:

1. In 2 psqls, run the deadlock test case. Deadlock is detected in 1sec.
2. Set deadlock_timeout = 15000 and reload the server.
3. Repeat step 1, deadlock is detected again in 1 sec.
4. Restart the server and repeat step 1, deadlock is detected in around
   15secs.

regards,
bhuvaneswaran

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Can not compile --with-tcl ???
Next
From: Stephan Szabo
Date:
Subject: Re: deadlock_timeout and pg_ctl reload