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

Re: [Tigerlead] BUG #5334: Version 2.22 of Perl Safe module breaks UTF8 PostgreSQL 8.4

From: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
To: "David E(dot) Wheeler" <david(dot)wheeler(at)pgexperts(dot)com>
Cc: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: [Tigerlead] BUG #5334: Version 2.22 of Perl Safe module breaks UTF8 PostgreSQL 8.4
Date: 2010-02-19 09:13:28
Message-ID: 20100219091328.GD373@timac.local (view raw or flat)
Thread:
Lists: pgsql-bugs
On Thu, Feb 18, 2010 at 01:36:59PM -0800, David E. Wheeler wrote:
> On Feb 18, 2010, at 10:09 AM, Tim Bunce wrote:
> 
> > It took a depressingly large number of intense hours to work out what
> > was going on and then more to try to work out a relatively clean solution.
> > 
> > The underlying problem is in perl and Safe but sadly there's no
> > reasonable way to fix Safe such that PostgreSQL would work without
> > changes.
> 
> Hrm. I don't have this bug with Safe 3.19, FWIW.

That's because Safe 1.19 (which I presume you meant) doesn't execute
closures 'inside' the Safe compartment. So when the regex executes at
runtime the C code looks up the utf8::SWASHNEW method without a problem.

Tim.

In response to

Responses

pgsql-bugs by date

Next:From: Tim BunceDate: 2010-02-19 09:30:41
Subject: Re: BUG #5334: Version 2.22 of Perl Safe module breaks UTF8 PostgreSQL 8.4
Previous:From: big colDate: 2010-02-19 02:32:12
Subject: Re: BUG #4785: Installation fails

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