X-Original-To: pgsql-jdbc-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6BA9DD1B172 for ; Sun, 18 Jul 2004 03:29:09 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 26623-09 for ; Sun, 18 Jul 2004 06:29:12 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 7D95FD1B182 for ; Sun, 18 Jul 2004 03:29:05 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i6I6T4OW028180; Sun, 18 Jul 2004 02:29:05 -0400 (EDT) To: "Dario V. Fassi" Cc: Oliver Jowett , pgsql-sql@postgresql.org, "pgsql-jdbc@postgresql.org" Subject: Re: [ADMIN] Migrate postgres databases from SQL_ASCII to UNICODE In-reply-to: <40F9B599.6080205@sistemat.com.ar> References: <40F98613.1060405@sistemat.com.ar> <16994.1090099096@sss.pgh.pa.us> <40F9B599.6080205@sistemat.com.ar> Comments: In-reply-to "Dario V. Fassi" message dated "Sat, 17 Jul 2004 20:26:17 -0300" Date: Sun, 18 Jul 2004 02:29:04 -0400 Message-ID: <28179.1090132144@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/227 X-Sequence-Number: 10611 "Dario V. Fassi" writes: >> SQL_ASCII is not an encoding (it's more like the absence of knowledge >> about an encoding). What is the data actually stored as? > Yes you are right , the original data come from a DB2 with CodePage > IBM-850 and was inserted without complains in a Postgres 7.3.6 with > SQL_ASCII. Ugh. You'll have to work out how to convert that codepage to one of the encodings that PG supports. Or else add it as a supported encoding (I'm not sure how hard that is, but it's not out of the question). regards, tom lane