Thread: [Fwd: [JDBC] Problem: upgrade from 7.1.3 to 7.2.1 ( database encode with ENC_TW)]
[Fwd: [JDBC] Problem: upgrade from 7.1.3 to 7.2.1 ( database encode with ENC_TW)]
From
Dave Cramer
Date:
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@gforce.ods.org> To: pgsql-jdbc@postgresql.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 it return following error... ------------------------>8--------------------------- . . NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index 'student_pk' for table 'student' CREATE ERROR: copy: line 2, Invalid EUC_TW character sequence found (0xae65) lost synchronization with server, resetting connection ERROR: copy: line 1, Invalid EUC_TW character sequence found (0xb27a) lost synchronization with server, resetting connection ERROR: copy: line 1, Invalid EUC_TW character sequence found (0xaa4d) lost synchronization with server, resetting connection ERROR: copy: line 1, Invalid EUC_TW character sequence found (0xb371) lost synchronization with server, resetting connection ERROR: copy: line 2, Invalid EUC_TW character sequence found (0xbc42) lost synchronization with server, resetting connection ERROR: copy: line 1, Invalid EUC_TW character sequence found (0xa470) lost synchronization with server, resetting connection ERROR: copy: line 1, Invalid EUC_TW character sequence found (0xa656) lost synchronization with server, resetting connection ERROR: copy: line 3, Invalid EUC_TW character sequence found (0xad50) lost synchronization with server, resetting connection CREATE CREATE . . ------------------------>8--------------------------- Please help. Gordon ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [Fwd: [JDBC] Problem: upgrade from 7.1.3 to 7.2.1 ( database encodewith ENC_TW)]
From
"Darko Prenosil"
Date:
----- Original Message ----- From: "Dave Cramer" <dave@fastcrypt.com> To: <pgsql-general@postgresql.org> Cc: <gordon@gforce.ods.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@gforce.ods.org> > To: pgsql-jdbc@postgresql.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.