Bruce Momjian <[EMAIL PROTECTED]> writes:
> Stephan Szabo wrote:
>> 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, a
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, e
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
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,
