Re: [Fwd: [JDBC] Problem: upgrade from 7.1.3 to 7.2.1 ( database encodewith ENC_TW)]

----- Original Message -----
From: "Dave Cramer" <dave(at)fastcrypt(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Cc: <gordon(at)gforce(dot)ods(dot)org>
Sent: Wednesday, May 15, 2002 11:53 AM
Subject: [GENERAL] [Fwd: [JDBC] Problem: upgrade from 7.1.3 to 7.2.1 (
database encodewith ENC_TW)]

> This message was posted to the jdbc list. I don't have the answer, but
> perhaps someone is familiar with the problem?
>
> Dave
> -----Forwarded Message-----
>
> From: Gordon Luk <gordon(at)gforce(dot)ods(dot)org>
> To: pgsql-jdbc(at)postgresql(dot)org
> Subject: [JDBC] Problem: upgrade from 7.1.3 to 7.2.1 ( database encode
with ENC_TW)
> Date: 15 May 2002 16:27:06 +0800
>
> Hi all,
>
> Problem as my letter subject, my upgrade procedure also just follow the
> simple.
>
> 1. compile 7.2.1 with multi-byte...with encode..
> 2. install ...
> 3. createdb -E EUC_TW mydatabase
> 4. psql mydatabase < dump_backup_from_my_old_database.txt
>

Does dump_backup_from_my_old_database.txt contains command:

SET CLIENT ENCODING TO 'EUC_TW'

Maybe it is not a default client encoding at Your system, and psql uses some
other client encoding ?
Similar errors I got when I tried to send LATIN2 dump using SQL_ASCII client
encoding.