Re: invalid UTF-8 via pl/perl

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Hannu Krosing <hannu(at)2ndquadrant(dot)com>
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 15:25:36
Message-ID: 4B9A5CF0.7000508@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hannu Krosing wrote:
> 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 ?
>

I wasn't going to. The previous fixes weren't backpatched either, and in
general when we have plugged encoding holes the changes have not been
backpatched, on the grounds that it would be a behaviour change, e.g.
when we tightened things a lot for 8.3.

I think there an outstanding TODO to plug the other PLs, however. It's a
pity it has to be done over and over for each PL. Maybe we need some new
versions of some of the SPI calls that would do the checking so it could
be centralized.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-03-12 15:40:01 Re: buildfarm logging versus embedded nulls
Previous Message Tom Lane 2010-03-12 15:18:53 Re: buildfarm logging versus embedded nulls