Skip site navigation (1) Skip section navigation (2)

Re: BUG #6097: Server crash when enabling custom_variable_classes

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: (view raw, whole thread or download thread mbox)
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

In response to

pgsql-bugs by date

Next:From: Angel DabovDate: 2011-07-08 15:09:35
Subject: BUG #6102: JDBC BIND Source IP Address
Previous:From: DmitryDate: 2011-07-08 11:33:09
Subject: BUG #6101: ALTER TABLE hangs with AccessExclusiveLock

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group