Re: guc patch: Make variables fall back to default values

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: guc patch: Make variables fall back to default values
Дата
Msg-id 200703131547.41285.peter_e@gmx.net
обсуждение исходный текст
Ответ на Re: guc patch: Make variables fall back to default values  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-patches
Tom Lane wrote:
> The thing that I was wondering about is the same Joachim mentioned:
> how is it that the regression test ever worked?  The answer is that
> it's not really testing custom variables, because it doesn't try to
> set plperl.use_strict until after plperl has been loaded into the
> current session.

I think that the sole purpose of c_v_c is to allow custom variables in
the configuration file, because that is possibly read before modules
are loaded.  Basically it just means that "prefix.*" is not rejected.
In a session, it doesn't make a difference what c_v_c is set to; the
variable needs to be registered period.  However, if the registration
code runs only when the module is invoked for the first time rather
than at the start of the session (as in the case of plperl), then it's
apparently impossible to set a variable in a session before the first
call.  It's all very weird.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

В списке pgsql-patches по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: guc patch: Make variables fall back to default values
Следующее
От: Joachim Wieland
Дата:
Сообщение: Re: guc patch: Make variables fall back to default values