Re: deadlock_timeout and pg_ctl reload - Mailing list pgsql-bugs

From Stephan Szabo
Subject Re: deadlock_timeout and pg_ctl reload
Date
Msg-id 20030721102806.Y4254-100000@megazone.bigpanda.com
Whole thread Raw
In response to deadlock_timeout and pg_ctl reload  ("A.Bhuvaneswaran" <bhuvan@symonds.net>)
Responses Re: deadlock_timeout and pg_ctl reload
List pgsql-bugs
On Mon, 21 Jul 2003, A.Bhuvaneswaran wrote:

> 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.

It looks like deadlock_timeout is set PGC_POSTMASTER so it's not
supposed to be reread on SIGHUP (reload) but only on postmaster start.

pgsql-bugs by date:

Previous
From: "A.Bhuvaneswaran"
Date:
Subject: deadlock_timeout and pg_ctl reload
Next
From: Boris Folgmann
Date:
Subject: Silent deadlock