Re: Possible problem with pg_reload_conf() and view pg_settings
От | Tony Caduto |
---|---|
Тема | Re: Possible problem with pg_reload_conf() and view pg_settings |
Дата | |
Msg-id | 436C39BD.5040905@amsoftwaredesign.com обсуждение исходный текст |
Ответ на | Re: Possible problem with pg_reload_conf() and view pg_settings (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Possible problem with pg_reload_conf() and view pg_settings
|
Список | pgsql-hackers |
Andrew Dunstan wrote: > > > Qingqing Zhou wrote: > >> >> test=# LOG: received SIGHUP, reloading configuration files >> >> test=# select setting from pg_settings where name = >> 'constraint_exclusion'; >> setting >> --------- >> off >> (1 row) >> >> test=# select setting from pg_settings where name = >> 'constraint_exclusion'; >> setting >> --------- >> on >> (1 row) >> >> >> -- Seems that's due to delay of process SIGHUP ... >> >> >> >> > > What's the delay? 1s? 5? 10? > > cheers > > andrew > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > > hmm, I waited for at least 1 minute after doing the reload and it was never updated. It seemed at the time that the only way to get a updated pg_settings view was to actually restart the server. I plan on doing some more testing on Saturday. Tony
В списке pgsql-hackers по дате отправления: