"Maxim Boguk" <Maxim(dot)Boguk(at)gmail(dot)com> writes:
> Test case simple:
> start server with empty custom_variable_classes
> Then add to config file:
> custom_variable_classes = 'something' # list of custom
> variable class names
> something.location = 'ru'
> And then perform
> select pg_reload_conf();
> Ooops... you have no more working server (but client connections staying
Hmm ... it's not exactly a crash, but an intentional postmaster exit;
the log shows
LOG: received SIGHUP, reloading configuration files
LOG: parameter "custom_variable_classes" changed to "something"
FATAL: unrecognized configuration parameter "something.location"
Nonetheless, it's clearly not the desired behavior :-(. Will look.
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Angel Dabov||Date: 2011-07-08 15:09:35|
|Subject: BUG #6102: JDBC BIND Source IP Address|
|Previous:||From: Dmitry||Date: 2011-07-08 11:33:09|
|Subject: BUG #6101: ALTER TABLE hangs with AccessExclusiveLock|