Janine Sisk wrote:
>> 0xEDA7A1 (UTF-8) corresponds to UNICODE code point 0xD9E1, which,
>> when interpreted as a high surrogare and followed by a low surrogate,
>> would correspond to the UTF-16 encoding of a code point
>> between 0x88400 and 0x887FF (depending on the value of the low surrogate).
>
On Jan 18, 2008, at 12:00 AM, Albe Laurenz wrote:
0xEDA7A1 (UTF-8) corresponds to UNICODE code point 0xD9E1, which,
when interpreted as a high surrogare and followed by a low surrogate,
would correspond to the UTF-16 encoding of a code point
between 0x88400 and 0x887FF (depending on the value of
Tom Lane wrote:
>> But I'm still getting this error when loading the data into the new
>> database:
>
>> ERROR: invalid byte sequence for encoding "UTF8": 0xeda7a1
>
> The reason PG doesn't like this sequence is that it corresponds to
> a Unicode "surrogate pair" code point, which is not suppo
Janine Sisk <[EMAIL PROTECTED]> writes:
> But I'm still getting this error when loading the data into the new
> database:
> ERROR: invalid byte sequence for encoding "UTF8": 0xeda7a1
The reason PG doesn't like this sequence is that it corresponds to
a Unicode "surrogate pair" code point, which
Hi all,
I'm moving a database from PG 7.2.4 to 8.2.6. I have already run
iconv on the dump file like so:
iconv -c -f UTF-8 -t UTF-8 -o out.dmp in.dmp
But I'm still getting this error when loading the data into the new
database:
ERROR: invalid byte sequence for encoding "UTF8": 0xeda7a1
