Re: First feature patch for plperl - draft [PATCH]
От | Tom Lane |
---|---|
Тема | Re: First feature patch for plperl - draft [PATCH] |
Дата | |
Msg-id | 28618.1259952660@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: First feature patch for plperl - draft [PATCH] ("David E. Wheeler" <david@kineticode.com>) |
Ответы |
Re: First feature patch for plperl - draft [PATCH]
Re: First feature patch for plperl - draft [PATCH] |
Список | pgsql-hackers |
"David E. Wheeler" <david@kineticode.com> writes: > On Dec 4, 2009, at 10:36 AM, Tom Lane wrote: >> I vote a big no on this. > That's fine. It's relatively simple for an admin to create a Perl module that does everything she wants, call it PGInitor something, and then just make the GUC: > plperl.on_perl_init = 'use PGInit;' No, you missed the point: I'm objecting to having any such thing as plperl.on_perl_init, full stop. Aside from the points I already made, it's not even well defined. What is to happen if the admin changes the value when the system is already up? regards, tom lane
В списке pgsql-hackers по дате отправления: