X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1FE2FD1D067 for ; Wed, 21 Apr 2004 06:51:37 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 77342-06 for ; Wed, 21 Apr 2004 06:51:37 -0300 (ADT) Received: from curie.credativ.org (credativ.com [217.160.209.18]) by svr1.postgresql.org (Postfix) with ESMTP id 3D610D1BABA for ; Wed, 21 Apr 2004 06:51:35 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by curie.credativ.org (Postfix) with ESMTP id A9D0555F03; Wed, 21 Apr 2004 11:51:36 +0200 (CEST) Received: from www.credativ.de (pD95F9C49.dip.t-dialin.net [217.95.156.73]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by curie.credativ.org (Postfix) with ESMTP id 2530B55BEB; Wed, 21 Apr 2004 11:51:36 +0200 (CEST) Received: from farnsworth.credativ.de (farnsworth.credativ.de [172.26.14.18]) by www.credativ.de (Postfix) with ESMTP id F3B881C00D2; Wed, 21 Apr 2004 11:51:31 +0200 (CEST) From: Peter Eisentraut To: Frank Finner Subject: Re: Going from a DB using SQL_ASCII to UNICODE Date: Wed, 21 Apr 2004 11:51:30 +0200 User-Agent: KMail/1.6.1 Cc: pgsql-admin@postgresql.org, lloyd@middleware-company.com, eric@middleware-company.com References: <20040420070551.385713b2.postgresql@finner.de> In-Reply-To: <20040420070551.385713b2.postgresql@finner.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404211151.30593.peter_e@gmx.net> X-Virus-Scanned: by AMaViS at credativ.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/273 X-Sequence-Number: 13246 Am Dienstag, 20. April 2004 07:05 schrieb Frank Finner: > I answered to a similiar problem on the [GENERAL] list a few days ago. In > short: You can use "recode" in a pipe between dump and restore like > "pg_dump database|recode ascii..utf8|psql newdatabase" to get rid of > unicode problems while transferring from a different encoding. Please look > at my statements on the[GENERAL] list for the gory details. This is not necessary. You just need to set the client encoding correctly (not SQL_ASCII, but something like LATIN1). The encoding conversion happens automatically, as usual.