From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Maxim Boguk" <Maxim(dot)Boguk(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6097: Server crash when enabling custom_variable_classes |
Date: | 2011-07-08 14:53:57 |
Message-ID: | 27074.1310136837@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"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
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Angel Dabov | 2011-07-08 15:09:35 | BUG #6102: JDBC BIND Source IP Address |
Previous Message | Dmitry | 2011-07-08 11:33:09 | BUG #6101: ALTER TABLE hangs with AccessExclusiveLock |