 | |
Re: [BUGS] deadlock_timeout and pg_ctl reload
mailing.database.pgsql-bugs mailing.database.pgsql-bugs
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Re: [BUGS] deadlock_timeout and pg_ctl reload -
07-21-2003
, 12:35 PM
|
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. |
supposed to be reread on SIGHUP (reload) but only on postmaster start.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
#2
| |||
| |||
|
|
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. |
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.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.