| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, "A(dot)Bhuvaneswaran" <bhuvan(at)symonds(dot)net>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: deadlock_timeout and pg_ctl reload |
| Date: | 2003-07-22 04:37:49 |
| Message-ID: | 3256.1058848669@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-07-22 16:02:34 | Re: [GENERAL] INSTEAD rule bug? |
| Previous Message | Bruce Momjian | 2003-07-22 01:59:41 | Re: deadlock_timeout and pg_ctl reload |