Skip site navigation (1) Skip section navigation (2)

Re: deadlock_timeout and pg_ctl reload

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: "A(dot)Bhuvaneswaran" <bhuvan(at)symonds(dot)net>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: deadlock_timeout and pg_ctl reload
Date: 2003-07-21 17:33:46
Message-ID: 20030721102806.Y4254-100000@megazone.bigpanda.com (view raw or flat)
Thread:
Lists: 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.




In response to

Responses

pgsql-bugs by date

Next:From: DeJuan JacksonDate: 2003-07-21 18:11:18
Subject: Re: [GENERAL] INSTEAD rule bug?
Previous:From: Bruce MomjianDate: 2003-07-21 15:20:05
Subject: Re: [BUGS] pg_tables view definition incorrect??

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group