Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA53916 for ; Mon, 10 May 1999 12:35:14 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id MAA07355; Mon, 10 May 1999 12:34:31 -0400 (EDT) From: Bruce Momjian Message-Id: <199905101634.MAA07355@candle.pha.pa.us> Subject: Re: [SQL] Strange behavior In-Reply-To: <9597.925250127@sss.pgh.pa.us> from Tom Lane at "Apr 27, 1999 05:55:27 pm" To: Tom Lane Date: Mon, 10 May 1999 12:34:31 -0400 (EDT) CC: Christophe Labouisse , pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=UNKNOWN-8BIT Content-Transfer-Encoding: 8bit > 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. OK, I agree, but I could never think of a better way. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026