X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 877DAD7A5C for ; Thu, 3 Nov 2005 18:41:34 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 08747-08 for ; Thu, 3 Nov 2005 22:41:29 +0000 (GMT) X-Greylist: delayed 00:06:20.281051 by SQLgrey- Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by svr1.postgresql.org (Postfix) with ESMTP id C1283D7215 for ; Thu, 3 Nov 2005 18:41:30 -0400 (AST) Received: by wproxy.gmail.com with SMTP id i3so155608wra for ; Thu, 03 Nov 2005 14:41:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=b0MG3xvC6n+m4eFkw4c44/4aLh47k6NGIy7JcII5nZBs/pGtJaA8jyV0XT+AKJNBSsEoIdPyEv7NDrectsaYU5AD6n9vvdguon5ntb9r3kbzVfa6Ox77mBgrFAmJY4T67Am2bRj6lEDoh/yag9iL+udDKvvZ0iKyQmZLrpvTrn4= Received: by 10.54.148.4 with SMTP id v4mr1014335wrd; Thu, 03 Nov 2005 14:35:13 -0800 (PST) Received: by 10.54.105.8 with HTTP; Thu, 3 Nov 2005 14:35:13 -0800 (PST) Message-ID: <6c21003b0511031435m3217574fk3013f41a4a265222@mail.gmail.com> Date: Thu, 3 Nov 2005 16:35:13 -0600 From: Don Drake To: pgsql-performance@postgresql.org Subject: Encoding on 8.0.4 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1643_24455213.1131057313075" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.056 required=5 tests=[AWL=0.055, HTML_MESSAGE=0.001] X-Spam-Score: 0.056 X-Spam-Level: X-Archive-Number: 200511/62 X-Sequence-Number: 15319 ------=_Part_1643_24455213.1131057313075 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I recently upgraded my DB from 7.4.3 to 8.0.4 and I've noticed the followin= g errors appearing in my serverlog: 2005-11-03 05:56:57 CST 127.0.0.1(38858) ERROR: Unicode characters greater than or equal to 0x10000 are not supported 2005-11-03 06:04:09 CST 127.0.0.1(38954) ERROR: invalid byte sequence for encoding "UNICODE": 0xe02d76 2005-11-03 06:04:21 CST 127.0.0.1(38964) ERROR: invalid byte sequence for encoding "UNICODE": 0xe02d76 2005-11-03 06:11:35 CST 127.0.0.1(39072) ERROR: Unicode characters greater than or equal to 0x10000 are not supported 2005-11-03 06:23:23 CST 127.0.0.1(39657) ERROR: invalid byte sequence for encoding "UNICODE": 0xd40d 2005-11-03 08:10:02 CST 127.0.0.1(44073) ERROR: invalid byte sequence for encoding "UNICODE": 0xe46973 2005-11-03 08:21:13 CST 127.0.0.1(44711) ERROR: Unicode characters greater than or equal to 0x10000 are not supported 2005-11-03 08:26:36 CST 127.0.0.1(44745) ERROR: invalid byte sequence for encoding "UNICODE": 0xc447 2005-11-03 08:40:59 CST 127.0.0.1(45087) ERROR: invalid byte sequence for encoding "UNICODE": 0xdd20 2005-11-03 09:14:52 CST 127.0.0.1(46009) ERROR: Unicode characters greater than or equal to 0x10000 are not supported I never received these errors on when running 7.4.3. I used the default encodings on 7.4.3 and I tried chaning client_encoding from sql_ascii to UNICODE and I'm still seeing this. I'm storing in a text data type email that contains other characterset characters. Any ideas on how to resolve this? -Don -- Donald Drake President Drake Consulting http://www.drakeconsult.com/ http://www.MailLaunder.com/ http://www.mobilemeridian.com/ 312-560-1574 ------=_Part_1643_24455213.1131057313075 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I recently upgraded my DB from 7.4.3 to 8.0.4 and I've noticed the followin= g errors appearing in my serverlog:


2005-11-03 05:56:57 CST 127.0.0.1(38858) ERROR:  Unicode characters gr= eater than or equal to 0x10000 are not supported
2005-11-03 06:04:09 CST 127.0.0.1(38954) ERROR:  invalid byte sequence= for encoding "UNICODE": 0xe02d76
2005-11-03 06:04:21 CST 127.0.0.1(38964) ERROR:  invalid byte sequence= for encoding "UNICODE": 0xe02d76
2005-11-03 06:11:35 CST 127.0.0.1(39072) ERROR:  Unicode characters gr= eater than or equal to 0x10000 are not supported
2005-11-03 06:23:23 CST 127.0.0.1(39657) ERROR:  invalid byte sequence= for encoding "UNICODE": 0xd40d
2005-11-03 08:10:02 CST 127.0.0.1(44073) ERROR:  invalid byte sequence= for encoding "UNICODE": 0xe46973
2005-11-03 08:21:13 CST 127.0.0.1(44711) ERROR:  Unicode characters gr= eater than or equal to 0x10000 are not supported
2005-11-03 08:26:36 CST 127.0.0.1(44745) ERROR:  invalid byte sequence= for encoding "UNICODE": 0xc447
2005-11-03 08:40:59 CST 127.0.0.1(45087) ERROR:  invalid byte sequence= for encoding "UNICODE": 0xdd20
2005-11-03 09:14:52 CST 127.0.0.1(46009) ERROR:  Unicode characters gr= eater than or equal to 0x10000 are not supported

I never received these errors on when running 7.4.3.  I used the default encodings on 7.4.3 and I tried chaning client_encoding from sql_ascii to UNICODE and I'm still seeing this. I'm storing in a text data type email that contains other characterset characters.  

Any ideas on how to resolve this?

-Don

--
Donald Drake
President
Drake Consult= ing
http://www.drakeconsult.c= om/
http://www.MailLaunder.com/
http://www.mobilemeridia= n.com/
312-560-1574
------=_Part_1643_24455213.1131057313075--