Re: UTF8 conversion differences from v8.1.3 to v8.1.4

From: Eric Faulhaber <ecf(at)goldencode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: UTF8 conversion differences from v8.1.3 to v8.1.4
Date: 2006-07-19 21:24:53
Message-ID: 44BEA325.30309@goldencode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>> The fact is that if you're using binary format paramaters and output
>> you can put embedded nulls into strings and get them back out.
>
> Not any more ;-)
>

OK, but now that this "feature" has been removed in 8.1.4, how is this
supposed to be handled, given that we don't control what string data
we're handed? How does psql deal with it?

>> By changing a
>> few strcmps to memcmps you can get sane behaviour for sorting a several
>> other operations.
>
> Given the lack of "memcoll", that proposal isn't going to fly ...
> at least not until we replace all the locale support code with something
> else (that hopefully will be null-clean).
>
> regards, tom lane

Thanks,
Eric

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Cornelia Boenigk 2006-07-19 21:30:35 Re: Problem creating a function - solved
Previous Message Tom Lane 2006-07-19 21:14:27 Re: Problem creating a function