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

From Tom Lane
Subject Re: deadlock_timeout and pg_ctl reload
Date
Msg-id 3256.1058848669@sss.pgh.pa.us
Whole thread Raw
In response to Re: deadlock_timeout and pg_ctl reload  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-bugs
Bruce Momjian <pgman@candle.pha.pa.us> 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, and reload doesn't happen at the same instant for all
> backend.

Yeah, I've forgotten the details, but I'm pretty sure we were worried
about race conditions or missed timeouts of some sort if we allowed
deadlock_timeout to change on-the-fly.  Try digging in the archives
if you want the whole scoop.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: deadlock_timeout and pg_ctl reload
Next
From: Alex Rodin
Date:
Subject: PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1