X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 69D77D1ED17 for ; Mon, 29 Mar 2004 07:33:24 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 41045-04 for ; Mon, 29 Mar 2004 03:33:24 -0400 (AST) Received: from post.rzg.mpg.de (post.rzg.mpg.de [130.183.9.21]) by svr1.postgresql.org (Postfix) with ESMTP id 4B821D1EDB3 for ; Mon, 29 Mar 2004 03:33:16 -0400 (AST) Received: from zim03 (zim03.ipp.mpg.de [130.183.2.228]) by post.rzg.mpg.de (8.9.2/8.9.2) with ESMTP id JAA16014; Mon, 29 Mar 2004 09:33:17 +0200 From: "Bulatovic Natasa" To: "'Markus Bertheau'" , "'Tom Lane'" Cc: Subject: Re: Invalid Unicode Character Sequence found Date: Mon, 29 Mar 2004 09:33:13 +0200 Message-ID: <002b01c41560$19f0c630$e402b782@ipp.ipp.mpg.de> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <1080381746.2050.3.camel@yarrow.bertheau.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/15 X-Sequence-Number: 17390 Yes, indeed very strange. However, it is certainly fixed, because I also tried more advanced version of postgres and this bug was not in there. Regards Natasa > -----Original Message----- > From: Markus Bertheau [mailto:twanger@bluetwanger.de]=20 > Sent: Saturday, March 27, 2004 11:02 AM > To: Tom Lane > Cc: Bulatovic Natasa; pgsql-sql@postgresql.org > Subject: Re: [SQL] Invalid Unicode Character Sequence found >=20 >=20 > =F7 =F0=D4=CE, 26.03.2004, =D7 22:43, Tom Lane =D0=C9=DB=C5=D4: > > "Bulatovic Natasa" writes: > > > select id, title from docs where title like 'z%'; or > > > select id, title from docs where title like 'Z%'; > > > It reports the following error: > > > ERROR: Invalid UNICODE character sequence found (0xc000) > >=20 > > This is fixed in 7.3.6. >=20 > I remember to have stumbled over this bug, too. I poked=20 > around in the code a bit but found nothing that hinted to=20 > cause of the bug. So I wonder what the cause of this bug was? >=20 > --=20 > Markus Bertheau >=20 >=20