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

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

From: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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 UPDATE v3 [PATCH]
Date: 2010-01-30 14:25:55
Message-ID: 20100130142555.GE1141@timac.local (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, Jan 29, 2010 at 09:10:48PM -0500, Andrew Dunstan wrote:
> Tim Bunce wrote:
> >This is an updated version of the third of the patches to be
> >split out from the former 'plperl feature patch 1'.
> >
> >It includes changes following discussions with Tom Lane and others.
> >
> >Changes in this patch:
> >
> >- Added plperl.on_perl_init GUC for DBA use (PGC_SIGHUP)
> >   SPI functions are not available when the code is run.
> >
> >- Added interpreter destruction behaviour
> >   Hooked via on_proc_exit().
> >   Only has any effect for normal shutdown.
> >   END blocks, if any, are run.
> >   SPI functions will die if called at this time.
> >
> >This updated version no longer tries to call object destructors.
> >I've added a note in the Limitations section of the PL/Perl docs.
> >It also adds a PERL_SET_CONTEXT() that's needed but was missing.
> I have committed this.

Many thanks.

> Tim, can you rebase the last two patches against current CVS HEAD?



In response to

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2010-01-30 14:38:31
Subject: Re: New VACUUM FULL
Previous:From: Simon RiggsDate: 2010-01-30 14:05:40
Subject: Re: New VACUUM FULL

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