Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id A52E32E2F61 for ; Thu, 17 Jan 2008 02:09:39 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 75817-01-10 for ; Thu, 17 Jan 2008 02:09:36 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id E3E482E01AC for ; Thu, 17 Jan 2008 02:09:02 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id m0H690kR004043; Thu, 17 Jan 2008 01:09:00 -0500 (EST) To: "Benjamin Krajmalnik" cc: pgsql-admin@postgresql.org Subject: Re: Strange client encoding issue In-reply-to: References: <200801162332.17449.rossacher@bluewin.ch> Comments: In-reply-to "Benjamin Krajmalnik" message dated "Wed, 16 Jan 2008 22:16:50 -0700" Date: Thu, 17 Jan 2008 01:09:00 -0500 Message-ID: <4042.1200550140@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/199 X-Sequence-Number: 27973 "Benjamin Krajmalnik" writes: > The error is most definitely being generated by the ODBC connection. > What can be causing the ODBC driver to set the client encoding to Latin9 > implicitly? Dunno, but the folks who would know that hang out in the pgsql-odbc list. regards, tom lane