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

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

From: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alex Hunsaker <badalex(at)gmail(dot)com>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>,pgsql-bugs(at)postgresql(dot)org,"David E(dot) Wheeler" <david(dot)wheeler(at)pgexperts(dot)com>
Subject: Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0)
Date: 2010-02-25 18:01:07
Message-ID: 20100225180107.GN1018@timac.local (view raw or flat)
Thread:
Lists: pgsql-bugs
On Wed, Feb 24, 2010 at 10:58:17PM -0500, Tom Lane wrote:
> Alex Hunsaker <badalex(at)gmail(dot)com> writes:
> > On Wed, Feb 24, 2010 at 20:37, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:
> >> On Wed, Feb 24, 2010 at 20:19, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >>> Seems entirely unacceptable.
> 
> >> I think we will see if we can get this fixed on the Safe/perl side then.
> 
> > BTW the trade off here is we revert back to sort { $a <=> $b } not
> > working.  That is if you could call it a trade off... The level of
> > breaking is not really comparable :)
> 
> That's two unacceptable alternatives, you need to find a third one.
> I think most people will have no trouble settling on "do not update
> to Safe 2.2x" if you don't offer a better solution than these.

I believe the next version of Safe will revert to Safe 1.19 behaviour
because the side effects of the change in 2.20 are too severe for it to
be left enabled by default.

Tim.

In response to

Responses

pgsql-bugs by date

Next:From: David E. WheelerDate: 2010-02-25 18:04:44
Subject: Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0)
Previous:From: Tom LaneDate: 2010-02-25 14:38:46
Subject: Re: BUG #5345: non-administrator users cannot create databases with special encoding

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