| From: | Hannu Krosing <hannu(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: invalid UTF-8 via pl/perl |
| Date: | 2010-03-12 14:32:19 |
| Message-ID: | 1268404339.32436.41.camel@hvost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2010-03-08 at 21:52 -0500, Andrew Dunstan wrote:
>
> Tom Lane wrote:
> > Hannu Krosing <hannu(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-03-12 15:18:53 | Re: buildfarm logging versus embedded nulls |
| Previous Message | Merlin Moncure | 2010-03-12 12:32:27 | Re: Dyamic updates of NEW with pl/pgsql |