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 4D422D1E2A0 for ; Thu, 11 Mar 2004 16:33:36 +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 20492-02 for ; Thu, 11 Mar 2004 12:33:24 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 1DA52D1BA6E for ; Thu, 11 Mar 2004 12:30:04 -0400 (AST) 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 i2BG3Hnv020282; Thu, 11 Mar 2004 11:03:17 -0500 (EST) To: "Rute Solipa" Cc: email_daniel_h@yahoo.com.br, pgsql-sql@postgresql.org Subject: Re: About pg_dump In-reply-to: <016701c40779$bbf9bd00$97ed89c1@etur> References: <404F9DFE.7000306@yahoo.com.br> <016701c40779$bbf9bd00$97ed89c1@etur> Comments: In-reply-to "Rute Solipa" message dated "Thu, 11 Mar 2004 15:01:29 +0000" Date: Thu, 11 Mar 2004 11:03:17 -0500 Message-ID: <20281.1079020997@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/132 X-Sequence-Number: 17231 "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