| From: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
|---|---|
| To: | Alex Hunsaker <badalex(at)gmail(dot)com> |
| Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5334: Version 2.22 of Perl Safe module breaks UTF8 PostgreSQL 8.4 |
| Date: | 2010-02-19 21:00:34 |
| Message-ID: | 20100219210034.GK373@timac.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Feb 19, 2010 at 09:32:38AM -0700, Alex Hunsaker wrote:
> On Fri, Feb 19, 2010 at 09:18, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:
> > It seems to me a more correct fix would be to require utf8; inside of
> > the safe like we do strict.
> > ....
> > Id favor this approach as if you have utf8 strings the likely hood
> > that you want ::upgrade, ::downgrade, ::encode, ::valid or ::is_utf8
> > is fairly high. Then again, no one has complained thus far... Maybe
> > thats just me :)
>
> On second thought, I dont think we should import any of those by
> default. And your hack for just SWASHNEW is better.
Here's the corresponding perlbug http://rt.perl.org/rt3/Ticket/Display.html?id=72942
I'll retest 8.4 and 9.0 against this on Monday.
Tim.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bob Lunney | 2010-02-19 21:13:28 | Cache lookup failure for index during pg_dump |
| Previous Message | Tim Bunce | 2010-02-19 20:56:32 | Re: [Tigerlead] BUG #5334: Version 2.22 of Perl Safe module breaks UTF8 PostgreSQL 8.4 |