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

Re: CommitFest Status Summary - 2010-02-14

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: CommitFest Status Summary - 2010-02-14
Date: 2010-02-16 21:42:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

Tim Bunce wrote:
> On Sun, Feb 14, 2010 at 10:14:28PM -0500, Andrew Dunstan wrote:
>> Robert Haas wrote:
>>> We're down to 5 patches remaining, and 1 day remaining, so it's time
>>> to try to wrap things up.
>>> * Package namespace and Safe init cleanup for plperl.  Andrew Dunstan
>>> is taking care of this one, I believe.
>> I will get this in, with changes as discussed recently.
> Here's a small extra patch for your consideration.
> It addresses a couple of minor loose-ends in plperl:
> - move on_proc_exit() call to after the plperl_*_init() calls
>     so on_proc_exit will only be called if plperl_*_init() succeeds
>     (else there's a risk of on_proc_exit consuming all the exit hook slots)
> - don't allow use of Safe version 2.21 as that's broken for PL/Perl.

I have committed all the plperl changes that were under discussion, 
including this, and the change to the log level of perl warnings.

Thanks for all your work, Tim, you have certainly given plperl a huge 
booster shot.



In response to


pgsql-hackers by date

Next:From: Tim BunceDate: 2010-02-16 22:06:00
Subject: Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl
Previous:From: Andrew DunstanDate: 2010-02-16 21:39:52
Subject: pgsql: Clean up package namespace use and use of Safe in plperl.

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