Re: Add on_perl_init and proper destruction to plperl [PATCH]

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: Add on_perl_init and proper destruction to plperl [PATCH]
Дата
Msg-id 4B5F8019.2020501@dunslane.net
обсуждение исходный текст
Ответ на Add on_perl_init and proper destruction to plperl [PATCH]  (Tim Bunce <Tim.Bunce@pobox.com>)
Ответы Re: Add on_perl_init and proper destruction to plperl [PATCH]  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers

Tim Bunce wrote:
> - Added plperl.on_perl_init GUC for DBA use (PGC_SIGHUP)
>     SPI functions are not available when the code is run.
>
> - Added normal interpreter destruction behaviour
>     END blocks, if any, are run then objects are
>     destroyed, calling their DESTROY methods, if any.
>     SPI functions will die if called at this time.
>   

OK, we've made good progress with the PL/Perl patches, and this one is 
next on the queue.

It should also be noted that as proposed END blocks will not run at all 
in the postmaster, even if perl is preloaded in the postmaster and the 
preloaded code sets END handlers. That makes setting them rather safer, 
ISTM.

So, are there still objections to applying this patch?

(Note, this is different from the proposal to specify on_trusted_init 
and on_untrusted_init handlers. The on_perl_init handler would be run on 
library load, and is mainly for the purpose of preloading perl modules 
and the like).

cheers

andrew




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

Предыдущее
От: David Christensen
Дата:
Сообщение: Patch: psql \whoami option
Следующее
От: Marko Tiikkaja
Дата:
Сообщение: Re: Review of Writeable CTE Patch