Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.1) with ESMTP id RAA66306 for ; Tue, 27 Apr 1999 17:56:42 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id RAA09599; Tue, 27 Apr 1999 17:55:28 -0400 (EDT) To: Christophe Labouisse cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Strange behavior In-reply-to: Your message of 27 Apr 1999 20:35:43 +0200 Date: Tue, 27 Apr 1999 17:55:27 -0400 Message-ID: <9597.925250127@sss.pgh.pa.us> From: Tom Lane Christophe Labouisse writes: >> As a temporary measure you could rebuild with USE_LOCALE turned on; >> the parser code is set up not to generate the <= clause if that's >> defined. But we need a better solution. > Hmm that's strange I though I compiled already with locale > enabled. Hmm. According to the cvs logs, Göran Thyni applied a patch on Feb 2 to disable the \377 thing when USE_LOCALE is defined. How old did you say your source was? Look in backend/parser/gram.y, routine makeIndexable(), to see if there is an #ifdef USE_LOCALE; also check gram.c to make sure it has the same text for the routine (I'm wondering if you might have an out-of-date gram.c...) > Anyway I'll check it again. Anyway I think that even without locale > this optimization can lead to incorrect result if you have a a field > starting with \377. I agree, the code is wrong even without funny sort ordering. We'll need to find another way. regards, tom lane