X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 331C5D1D269 for ; Thu, 11 Mar 2004 21:03:17 +0000 (GMT) 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 54344-10 for ; Thu, 11 Mar 2004 17:03:17 -0400 (AST) Received: from localhost.localdomain (unknown [200.245.23.5]) by svr1.postgresql.org (Postfix) with ESMTP id 266F2D1C9ED for ; Thu, 11 Mar 2004 17:03:09 -0400 (AST) Received: from yahoo.com.br (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id i2BLDIYC002051 for ; Thu, 11 Mar 2004 18:13:19 -0300 Message-ID: <4050D66E.4050706@yahoo.com.br> Date: Thu, 11 Mar 2004 18:13:18 -0300 From: Daniel Henrique Alves Lima Reply-To: email_daniel_h@yahoo.com.br User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Re: About pg_dump References: <404F9DFE.7000306@yahoo.com.br> <016701c40779$bbf9bd00$97ed89c1@etur> <20281.1079020997@sss.pgh.pa.us> In-Reply-To: <20281.1079020997@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/139 X-Sequence-Number: 17238 I've made a test and it seems ok to me. I'm using utf-8 encoding under postgresql 7.3.3. Tom Lane wrote: >"Rute Solipa" writes: > > >>it seems that the pg_dump command doesn't keep the encoding information. >> >> > >As of 7.4.2 it does emit a SET client_encoding. > >In prior releases, if you are manually creating the destination database >then you need to be careful to create it with the same encoding as before. > > regards, tom lane > >---------------------------(end of broadcast)--------------------------- >TIP 4: Don't 'kill -9' the postmaster > > >