X-Original-To: pgsql-sql-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id ED3F49FB2E2 for ; Wed, 30 Aug 2006 05:26:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 02756-05-2 for ; Wed, 30 Aug 2006 05:26:05 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.logix-tt.com (mail.logix-tt.com [212.211.145.186]) by postgresql.org (Postfix) with ESMTP id B216C9FB2F2 for ; Wed, 30 Aug 2006 05:25:44 -0300 (ADT) Received: from kingfisher.intern.logix-tt.com (p549D1C2A.dip0.t-ipconnect.de [84.157.28.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id CD0C465946 for ; Wed, 30 Aug 2006 10:27:51 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id 85FA5181C1BBD for ; Wed, 30 Aug 2006 10:26:04 +0200 (CEST) Message-ID: <44F54B9C.4040200@logix-tt.com> Date: Wed, 30 Aug 2006 10:26:04 +0200 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Thunderbird 1.5.0.4 (X11/20060713) MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Re: UTF8 Vs Latin9 and valid encoding. References: <20060830044853.15728.qmail@web53007.mail.yahoo.com> In-Reply-To: <20060830044853.15728.qmail@web53007.mail.yahoo.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.171 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200608/235 X-Sequence-Number: 26193 Hi, Marcelo, Marcelo . wrote: > I receive the error msg: > ERROR: invalid UTF-8 byte sequence detected near byte > 0xf1 > > Isn't UTF-8 the same as UNICODE where it encapsulates > all other coding schemes including latin9? Yes, it is. But it seems that your client and the server disagree on the encoding they use. I think the problem is that your client (psql, I presume) uses latin9 to communicate with the server, but the server assumes the client uses utf8. in psql, you can use \encoding to show the encoding psql uses, and "show client_encoding;" to show the encoding the server thinks the client uses. Try one of: SET client_encoding TO LATIN9; -- Tell server: client uses latin9 \encoding LATIN9; -- Set clients encoding You can also set UTF-8 here, the server will convert between the client and database encoding (but it needs to know). HTH, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org