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

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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]
Date: 2010-01-26 23:51:53
Message-ID: 4B5F8019.2020501@dunslane.net (view raw or flat)
Thread:
Lists: 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



In response to

Responses

pgsql-hackers by date

Next:From: Marko TiikkajaDate: 2010-01-27 01:28:52
Subject: Re: Review of Writeable CTE Patch
Previous:From: David ChristensenDate: 2010-01-26 23:24:14
Subject: Patch: psql \whoami option

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