Skip site navigation (1) Skip section navigation (2)

Re: UTF-8 data migration problem in Postgresql 7.2

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: jm(dot)poure(at)freesurf(dot)fr
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org, Inoue(at)tpf(dot)co(dot)jp
Subject: Re: UTF-8 data migration problem in Postgresql 7.2
Date: 2002-02-20 00:50:55
Message-ID: 20020220095055B.t-ishii@sra.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-odbc
> I tried to migrate a UTF-8 database with Japanese content from Postgresql 
> 7.1.3 to Postgresql 7.2 unsucessfully.
> 
> I made a pg_dump of the 7.1.3 database and tried to upload it in 7.2.
> Error message was "Invalid Unicode character sequence found".
> 
> I tried to upload data in a fresh PostgreSQL 7.1.3 database and everything 
> worked OK. The problem can be reproduced on PostgreSQL 7.2.
> 
> Do not hesitate to ask me for a pg_dump of the involved tables. I cannot 
> submit them on the list for privacy reasons. Thanks for your help.

I have received the test data and got:

psql:dump_error.sql:40: ERROR:  copy: line 1, Invalid UNICODE character sequence found (0xe38227)

The error messages shows your data contains an invalid UTF-8 character
sequence. The first byte (e8) expects the UTF-8 sequence consists of 3
bytes, each of 8th bit on. However the third byte is 0x27, apparently
it does not satisfy the requirement. Check your data.
--
Tatsuo Ishii

In response to

Responses

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2002-02-20 02:41:32
Subject: Re: alter table drop column status
Previous:From: Philip WarnerDate: 2002-02-19 23:11:59
Subject: Re: pg_dump: use ALTER TABLE for PKs

pgsql-odbc by date

Next:From: kuolung linDate: 2002-02-20 02:28:20
Subject: post
Previous:From: Kristis MakrisDate: 2002-02-19 23:54:48
Subject: Are multiple selects of the same field allowed usingCRecordset::GetFieldValue() ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group