X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 128B29FB1CD for ; Thu, 24 Aug 2006 11:41:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 82866-01 for ; Thu, 24 Aug 2006 14:41:06 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 86F529FA6B1 for ; Thu, 24 Aug 2006 11:41:06 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k7OEf48F004646; Thu, 24 Aug 2006 10:41:05 -0400 (EDT) To: Gary Stainburn cc: pgsql-admin@postgresql.org Subject: Re: yum update now gives me UNICODE errors In-reply-to: <200608241343.00499.gary.stainburn@ringways.co.uk> References: <200608241343.00499.gary.stainburn@ringways.co.uk> Comments: In-reply-to Gary Stainburn message dated "Thu, 24 Aug 2006 13:43:00 +0100" Date: Thu, 24 Aug 2006 10:41:04 -0400 Message-ID: <4645.1156430464@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.816 tagged_above=0 required=5 tests=SPF_HELO_SOFTFAIL, SPF_SOFTFAIL X-Spam-Level: *** X-Archive-Number: 200608/267 X-Sequence-Number: 22810 Gary Stainburn writes: > ERROR: invalid byte sequence for encoding "UNICODE": 0xa3 > The problem is the £ (pound sterling) sign, but I never had any problems prior > to the update. Postgres didn't use to be quite as picky about the encoding as it is now. What you are sending it is not UTF-8, and you can no longer get away with pretending that it is. It looks like you're probably using Latin1 (ISO 8859-1) or something related. Assuming that that's what's really in your database, what I'd do is - dump the database - edit the SET client_encoding command at the head of the dump file to say the correct encoding - initdb in the correct locale (one using your encoding, not utf8) - reload data regards, tom lane