Re: Add on_perl_init and proper destruction to plperl [PATCH] - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Add on_perl_init and proper destruction to plperl [PATCH]
Date
Msg-id 4B604BFB.5090405@dunslane.net
Whole thread Raw
In response to Re: Add on_perl_init and proper destruction to plperl [PATCH]  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Add on_perl_init and proper destruction to plperl [PATCH]  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>   
>> 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.
>>>       
>
>   
>> So, are there still objections to applying this patch?
>>     
>
> Yes.
>
>             
>   

I see I asked the wrong question. Start again.

What more should be done to make all or some of it acceptable?

cheers

andrew


pgsql-hackers by date:

Previous
From: David Christensen
Date:
Subject: Re: Patch: psql \whoami option
Next
From: Robert Haas
Date:
Subject: Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns