"Maxim Boguk" <maxim.bo...@gmail.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
> alive).
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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
