Re: deadlock_timeout and pg_ctl reload

Stephan Szabo wrote:
>
> 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.

I think it doesn't reload because we want to have the same timeouts for
all backends, and reload doesn't happen at the same instant for all
backend. A restart would get the new values, or should.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073