Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0) - Mailing list pgsql-bugs

From Alex Hunsaker
Subject Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0)
Date
Msg-id 34d269d41002251129j743c55e6jb7f8e57d4079113d@mail.gmail.com
Whole thread Raw
In response to Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0)  ("David E. Wheeler" <david.wheeler@pgexperts.com>)
Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0)  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-bugs
On Thu, Feb 25, 2010 at 12:20, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Alex Hunsaker <badalex@gmail.com> writes:
>> 3) patch postgres to fix the recursive issue (What I'm leaning towards)
>> [ fixes both issues ]
>
> How exactly would you propose doing that?

Well that's the thing, probably by what I described below that. Namely
get something working for 9.1 and after we know its good and solid see
if we can back patch it.  Unfeasible?  If its really really simple and
straight forward maybe we can find a -commiter willing to commit it
sooner.  But I'm dubious.  I think the feeling between me and Tim is
patching postgres is a last resort...  Maybe if its to fix both sort
{} and this it might be worth it. (That's at least how I parsed what
you said :) ).  Ill see if I can figure something out via straight
Safe tonight.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0)
Next
From: "David E. Wheeler"
Date:
Subject: Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0)