X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1D960D1B1EC for ; Tue, 29 Jun 2004 13:16:42 -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 64221-08 for ; Tue, 29 Jun 2004 16:16:32 +0000 (GMT) Received: from mail4.bluewin.ch (mail4.bluewin.ch [195.186.4.74]) by svr1.postgresql.org (Postfix) with ESMTP id 20A1AD1B23E for ; Tue, 29 Jun 2004 13:16:31 -0300 (ADT) Received: from server.ptools (195.186.211.189) by mail4.bluewin.ch (Bluewin AG 7.0.028) id 40D19C0700189C75 for pgsql-admin@postgresql.org; Tue, 29 Jun 2004 16:16:29 +0000 From: Ivo Rossacher To: pgsql-admin@postgresql.org Subject: Re: Change the character encoding of a database Date: Tue, 29 Jun 2004 18:16:31 +0200 User-Agent: KMail/1.6.2 References: <200406282338.25074.rossacher@bluewin.ch> <40E17CCD.5070003@wificom.com> In-Reply-To: <40E17CCD.5070003@wificom.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406291816.31311.rossacher@bluewin.ch> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200406/370 X-Sequence-Number: 14030 This did finaly work for me. I have to add that to get this working it is required to have a UTF-8 aware system on which the psql runs during import. Since the database server is not a UTF-8 system, my tries with this approche on the server only did fail. Thanks a lot. Best regards Ivo Rossacher Am Dienstag, 29. Juni 2004 16:29 schrieb James Cooper: > Ah yes, if there points for FAQ this would top the bill. My approach was > to dump the database, create a new one as UNICODE and then used a tool > called "recode" to convert the dumped database to UNICODE and the > imported into Postgre. > > http://recode.progiciels-bpi.ca/ > > Ivo Rossacher wrote: > > Hi All, > > > > I do have a database which was created with the encoding SQL_ASCII and > > used with German, French and Italien strings. Until recently there was > > only a Linux client, an all worked fine (Suse 8.1). Now there is a new > > Windows client which does have a different idea of the encoding. I did > > some tests and found out that the encoding UNICODE does work properly for > > both clients. The question now is how to change the encoding of database > > from SQL_ASCII to UNICODE? > > > > I did try to dump the database by pgdump database > dump.dmp, droped the > > database, recreate it with the encoding UNICODE and restore the dump by > > psql database < dump.dmp which worked after some small changes (change > > the client encoding to UNICODE) in the dump.dmp. Without the changes in > > the dump.dmp there was a error message about invalide codes and no import > > at all. With the changes there are still some encoding mistakes (wrong > > signes in the strings) but the import basically works. The server > > actually runs on the same machine as the client (Suse 8.1). I think there > > is a problem with the import because the linux system is not set to use > > UNICODE. Is there an way to get the data converted correctly? -- Ivo Rossacher