Re: First feature patch for plperl - draft [PATCH]

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: First feature patch for plperl - draft [PATCH]
Дата
Msg-id 28909.1259953528@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: First feature patch for plperl - draft [PATCH]  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: First feature patch for plperl - draft [PATCH]  ("David E. Wheeler" <david@kineticode.com>)
Re: First feature patch for plperl - draft [PATCH]  (Robert Haas <robertmhaas@gmail.com>)
Re: First feature patch for plperl - draft [PATCH]  (Tim Bunce <Tim.Bunce@pobox.com>)
Re: First feature patch for plperl - draft [PATCH]  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> So, do we look for another way to provide the functionality besides
> having a GUC, or is the functionality itself bad?

I don't think we want random Perl code running inside the postmaster,
no matter what the API to cause it is.  I might hold my nose for "on
load" code if it can only run in backends, though I still say that
it's a badly designed concept because of the uncertainty about who
will run what when.  Shlib load time is not an event that ought to be
user-visible.
        regards, tom lane


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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: Block-level CRC checks
Следующее
От: "David E. Wheeler"
Дата:
Сообщение: Re: First feature patch for plperl - draft [PATCH]