X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B96C311F6083 for ; Tue, 25 Apr 2006 06:54:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 65503-09 for ; Tue, 25 Apr 2006 06:54:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sydney.mailnetwork.co.uk (server88-208-192-113.live-servers.net [88.208.192.113]) by postgresql.org (Postfix) with ESMTP id C437911F6085 for ; Tue, 25 Apr 2006 06:53:58 -0300 (ADT) Received: from [213.146.143.243] (port=31895 helo=it020361) by sydney.mailnetwork.co.uk with esmtpa (Exim 4.60) (envelope-from ) id 1FYKF4-0000TK-Gz; Tue, 25 Apr 2006 10:53:58 +0100 Reply-To: From: "Andy Shellam" To: Cc: Subject: Re: Is it a bug ? Date: Tue, 25 Apr 2006 10:53:58 +0100 Organization: the mail network MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01C66856.8E219700" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <200604250953.k3P9rUxI022088@Citrus.usj.edu.lb> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 thread-index: AcZoPAuvtAL1fxDmSB6zFYZvsaQGDgACf9VwAAFUgdAAAHsn8AAAJfZg Message-Id: <20060425095358.C437911F6085@postgresql.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/264 X-Sequence-Number: 21433 This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C66856.8E219700 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Pascal, If this is a bug in 7.3, and it's not in later versions, I doubt the developers will be in any hurry to fix it, I don't know - maybe someone knows a quick patch fix, or if it was fixed in a later version of the 7.3 series - as that would only be a minor upgrade (e.g. 7.3.2 to 7.3.8 or something), and it wouldn't cause you much downtime. Andy _____ From: Pascal Tufenkji [mailto:ptufenkji@usj.edu.lb] Sent: 25 April 2006 10:51 am To: andy.shellam@mailnetwork.co.uk Subject: RE: [ADMIN] Is it a bug ? Hi Andy Actually no. I just tried it on Postgres 8.0.4 and there is no problem But is there no solution for the 7.3.0 version? Because we haven't upgraded our servers yet. Thx for your quick reply Pascal _____ From: Andy Shellam [mailto:andy.shellam@mailnetwork.co.uk] Sent: Tuesday, April 25, 2006 12:35 PM To: ptufenkji@usj.edu.lb Cc: pgsql-admin@postgresql.org Subject: RE: [ADMIN] Is it a bug ? Hi Pascal, 7.3 is now quite out-dated - have you tried the latest release, 8.1.3, to see if the problem is still present? Andy _____ From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Pascal Tufenkji Sent: 25 April 2006 10:02 am To: pgsql-admin@postgresql.org Subject: [ADMIN] Is it a bug ? Hi, I just noticed a bug in PostgreSQL 7.3.2 I don't know if it exists in other versions If I have a UNICODE database and I make the following query SELECT * FROM table where code like 'abcz%'; Or SELECT * FROM table where code like 'abcz_'; (or anything that ends with z% or z_) It gives the following error : ERROR: Invalid UNICODE character sequence found (0xc000) Other queries like SELECT * FROM table where code ilike 'abcz%'; SELECT * FROM table where code like '%abcz%'; Or the same query but in an SQL_ASCII database don't give the same error Is it a bug in Postgres ???? I'd appreciate an explanation Thx Pascal !DSPAM:14,444df0ae33699570057613! ------=_NextPart_000_001F_01C66856.8E219700 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi = Pascal,

 

If this is a bug in 7.3, and = it’s not in later versions, I doubt the developers will be in any hurry to = fix it, I don’t know – maybe someone knows a quick patch fix, or if it = was fixed in a later version of the 7.3 series – as that would only be = a minor upgrade (e.g. 7.3.2 to 7.3.8 or something), and it wouldn’t = cause you much downtime.

 

Andy

 


From: = Pascal Tufenkji [mailto:ptufenkji@usj.edu.lb]
Sent: 25 April 2006 10:51 = am
To: = andy.shellam@mailnetwork.co.uk
Subject: RE: [ADMIN] Is = it a bug ?

 

Hi = Andy

 

Actually = no…

I just tried it on Postgres 8.0.4 = and there is no problem

But is there no solution for the = 7.3.0 version?

Because we haven’t upgraded = our servers yet…

 

Thx for your quick = reply

Pascal

 


From: Andy = Shellam [mailto:andy.shellam@mailnetwork.co.uk]
Sent: Tuesday, April 25, = 2006 12:35 PM
To: = ptufenkji@usj.edu.lb
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] Is = it a bug ?

 

Hi = Pascal,

 

7.3 is now quite out-dated – = have you tried the latest release, 8.1.3, to see if the problem is still = present?

 

Andy

 


From: pgsql-admin-owner@postgresql.org = [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Pascal Tufenkji
Sent: 25 April 2006 10:02 = am
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Is it a = bug ?

 

Hi,

I just noticed a bug in = PostgreSQL 7.3.2

I don't know if it exists in = other versions

 

If I have a UNICODE database and = I make the following query

 

SELECT * FROM = table where code like 'abcz%';

Or =

SELECT * FROM = table where code like 'abcz_';

(or anything that ends with z% or = z_)

It gives the following error = :

ERROR:  Invalid UNICODE = character sequence found (0xc000)

 

Other queries like =

SELECT * FROM table where code = ilike 'abcz%';

SELECT * FROM table where code = like '%abcz%';

Or the same query but in = an SQL_ASCII database don’t = give the same error

 

Is it a bug in Postgres = ????

 

I’d appreciate an = explanation

 

Thx

Pascal

 

 

 

!DSPAM:14,444df0ae33699570057613!

------=_NextPart_000_001F_01C66856.8E219700--