Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id C67A264FCD2 for ; Thu, 18 Sep 2008 17:10:23 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 19609-10 for ; Thu, 18 Sep 2008 17:10:20 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from cerga.lunarpages.com (cerga.lunarpages.com [209.200.229.150]) by postgresql.org (Postfix) with ESMTP id 9408764FCC2 for ; Thu, 18 Sep 2008 17:10:20 -0300 (ADT) Received: from c-24-14-55-166.hsd1.il.comcast.net ([24.14.55.166] helo=[192.168.107.89]) by cerga.lunarpages.com with esmtpa (Exim 4.69) (envelope-from ) id 1KgPpR-0006Re-SR for pgsql-admin@postgresql.org; Thu, 18 Sep 2008 13:10:17 -0700 Message-ID: <48D2B5B0.9020708@earthcomber.com> Date: Thu, 18 Sep 2008 15:10:24 -0500 From: Randall Wilson User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: Re: Idle Error invalid byte sequence References: <48D273D8.7010603@earthcomber.com> <23674.1221761835@sss.pgh.pa.us> In-Reply-To: <23674.1221761835@sss.pgh.pa.us> Content-Type: multipart/mixed; boundary="------------060409000604090801050407" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cerga.lunarpages.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - earthcomber.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/203 X-Sequence-Number: 30296 This is a multi-part message in MIME format. --------------060409000604090801050407 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Yes, the encoding was changed from SQL_ASCII to UTF-8. Does the fact that it's an "Idle" error conform your theory that some client is causing the error? I thought the "Idle" error was caused by errors found during background processes, like vacuums. I made a plain text backup of the live database and I'm not having any luck grepping for the character. I may be doing it wrong. If I can't find it in the database dump, what does that tell us? Is it possibly in a template database. Thanks for your help, Randy Tom Lane wrote: > Randall Wilson writes: > >> We've got a PostgreSQL 8.1.11 database that started displaying these >> error messages almost immediately AFTER it was restored. >> ... >> Is there any way to figure out where the 0x8b character is? >> > > Hmm, did you perhaps change the database encoding from its previous > value? The most likely bet is that the bad encoding is arriving from a > client, which is evidently expecting to send something other than UTF8 > but not bothering to set client_encoding to tell what. > > regards, tom lane > > --------------060409000604090801050407 Content-Type: text/x-vcard; charset=utf-8; name="rwilson.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rwilson.vcf" begin:vcard fn:Randall Wilson n:Wilson;Randall org:Earthcomber, LLC;Development adr:Suite 114;;7777 Lake St.;River Forest;IL;60305;USA email;internet:rwilson@earthcomber.com title:Senior Software Engineer tel;work:708-366-1611 tel;cell:773-620-3042 x-mozilla-html:FALSE url:http://www.earthcomber.com version:2.1 end:vcard --------------060409000604090801050407--