Re: invalid UTF-8 via pl/perl - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: invalid UTF-8 via pl/perl
Date
Msg-id 1268404339.32436.41.camel@hvost
Whole thread Raw
In response to Re: invalid UTF-8 via pl/perl  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: invalid UTF-8 via pl/perl
List pgsql-hackers
On Mon, 2010-03-08 at 21:52 -0500, Andrew Dunstan wrote:
> 
> Tom Lane wrote:
> > Hannu Krosing <hannu@2ndquadrant.com> writes:
> >   
> >> So SPI interface should also be fixed, either from perl side, or maybe
> >> from inside SPI ?
> >>     
> >
> > SPI has every right to assume that data it's given is already in the
> > database encoding.
> >
> >             
> >   
> 
> Yeah, looks like we missed a few spots. I have added three more checks 
> that I think plug the remaining holes in plperl.
> 
> Hannu, please test again against CVS HEAD.

Seems to work now

Do you plan to back-port this ?

-- 
Hannu Krosing   http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability   Services, Consulting and Training




pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Dyamic updates of NEW with pl/pgsql
Next
From: Tom Lane
Date:
Subject: Re: buildfarm logging versus embedded nulls