Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 17F839FB1D3; Wed, 21 Mar 2007 00:32:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 94953-03; Wed, 21 Mar 2007 00:32:51 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by postgresql.org (Postfix) with ESMTP id 65CEE9FB1C4; Wed, 21 Mar 2007 00:32:52 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.8/8.13.8) with ESMTP id l2L3Wj3l043743 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Mar 2007 20:32:48 -0700 (MST) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.8/8.13.8) with ESMTP id l2L3WjV1046076; Tue, 20 Mar 2007 21:32:45 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.8/8.13.8/Submit) id l2L3WiJt046075; Tue, 20 Mar 2007 21:32:44 -0600 (MDT) (envelope-from mfuhr) Date: Tue, 20 Mar 2007 21:32:44 -0600 From: Michael Fuhr To: Claus Guttesen Cc: Karthikeyan Sundaram , pgsql-admin@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [SQL] ERROR: invalid byte sequence for encoding "UTF8": 0x92 Message-ID: <20070321033244.GA39959@winnie.fuhr.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/142 X-Sequence-Number: 24966 On Tue, Mar 20, 2007 at 09:06:25PM +0100, Claus Guttesen wrote: > >DBD::Pg::st execute failed: ERROR: invalid byte sequence for encoding > >"UTF8": 0x92 > >[for Statement "INSERT INTO longdescs (bug_id, who, bug_when, thetext, > >isprivate) > > Try to modify client_encoding in postgresql.conf to utf8 and restart your > db. The data is apparently not UTF-8 so client_encoding needs to be set to something else. 0x92 is a hint that the encoding might be Windows-1252 or Windows-1250 since that byte represents the right single quotation mark in those encodings; that's a common character in data that originated in Windows. Also, client_encoding can be set by the client without having to restart the backend. -- Michael Fuhr