Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id CDC4C2E0105 for ; Mon, 26 Nov 2007 14:58:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 94225-04-3 for ; Mon, 26 Nov 2007 14:58:36 -0400 (AST) Received: from cptec.inpe.br (guapira.cptec.inpe.br [150.163.140.191]) by postgresql.org (Postfix) with ESMTP id 7CB592E0116 for ; Mon, 26 Nov 2007 14:58:38 -0400 (AST) Received: from [150.163.140.242] (manoia.cptec.inpe.br [150.163.140.242]) by cptec.inpe.br (8.12.10/8.12.4) with ESMTP id lAQJ7wVb001524 for ; Mon, 26 Nov 2007 16:07:58 -0300 (EST) Message-ID: <474B174F.8050503@cptec.inpe.br> Date: Mon, 26 Nov 2007 16:58:23 -0200 From: =?ISO-8859-1?Q?Jos=E9_Roberto_Motta_Garcia?= User-Agent: Thunderbird 1.5 (X11/20060317) MIME-Version: 1.0 CC: pgsql-admin@postgresql.org Subject: Re: Restoring wrong accents References: <474726D9.4020907@cptec.inpe.br> <18370.1195849829@sss.pgh.pa.us> In-Reply-To: <18370.1195849829@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.031 tagged_above=0 required=5 tests=AWL=-0.261, BAYES_50=0.001, MISSING_HEADERS=1.292 X-Spam-Level: * X-Archive-Number: 200711/222 X-Sequence-Number: 27465 You where right. It's ok now, it was the old one "If you want it to be done correctly do it yourself". Tks a lot. Jose Roberto M. Garcia, MSc Analista de Sistemas - Grupo Banco de Dados Fone: (12) 3186-8405 -- A luta contra o aquecimento global depende de cada um de nós, faça sua parte, economize recursos naturais. -- http://www.cptec.inpe.br http://www.inpe.br Tom Lane wrote: > =?ISO-8859-1?Q?Jos=E9_Roberto_Motta_Garcia?= writes: > >> We're having problems restoring the characters correctly here. We have a >> 8.1 PG on Suse created with LATIN1 and pt_BR. As a latin language we use >> several special chars like á, ã, ç, í, etc. >> > > >> We made a dump -a and after restoring it to an also 8.1 PG on Suse >> created with LATIN1 and pt_BR we noticed that a lot of these special >> chars weren't restored correctly. We couldn't notice any rule for that, >> > > It seems highly unlikely that you actually had the same encoding in both > cases, since if that were the case no conversion would have occurred. > Please double-check the two database encodings. Also, what encoding is > called out in the first few lines of the dump file? > > regards, tom lane >