Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E90ED650713 for ; Tue, 15 Jul 2008 12:10:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 56934-09 for ; Tue, 15 Jul 2008 12:09:54 -0300 (ADT) Received: from mx1.hub.org (mx1.hub.org [200.46.208.106]) by postgresql.org (Postfix) with ESMTP id 41AFF65061F for ; Tue, 15 Jul 2008 12:10:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gauss.credativ.com (gauss.credativ.com [212.112.227.254]) by mx1.hub.org (Postfix) with ESMTP id 3D39EB078DD for ; Tue, 15 Jul 2008 12:09:54 -0300 (ADT) Received: from hawking.credativ.lan (exit.credativ.com [87.139.82.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id ACD17774F5; Tue, 15 Jul 2008 17:04:48 +0200 (CEST) From: Peter Eisentraut To: pgsql-admin@postgresql.org Subject: Re: Changing encoding Date: Tue, 15 Jul 2008 17:04:43 +0200 User-Agent: KMail/1.9.9 Cc: Carol Walter References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807151704.44182.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/132 X-Sequence-Number: 29742 Am Dienstag, 15. Juli 2008 schrieb Carol Walter: > I have some databases that use SQL ASCII or Latin1 encoding that need > to be UTF8. When I have drop the database and recreated it with the > correct encoding I get errors in restoring the data. How is this done? What is your PostgreSQL version? What is the exact command sequence? The sort of problem you describe is usually fixed by setting the client encoding correctly, but recent versions should do this automatically for dumps/restores.