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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]
Date: 2010-01-27 14:21:47
Message-ID: 4B604BFB.5090405@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-01-27 14:29:06 Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns
Previous Message David Christensen 2010-01-27 14:14:17 Re: Patch: psql \whoami option