Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0C0aXp63882 for ; Thu, 11 Jan 2001 19:36:33 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0C0aJJ13457; Thu, 11 Jan 2001 19:36:19 -0500 (EST) To: George Moga cc: pgsql-sql@postgresql.org Subject: Re: "SELECT" problem on 7.0.3 In-reply-to: <3A5DEFD4.CB51CF22@cicnet.ro> References: <3A5DEFD4.CB51CF22@cicnet.ro> Comments: In-reply-to George Moga message dated "Thu, 11 Jan 2001 19:39:32 +0200" Date: Thu, 11 Jan 2001 19:36:18 -0500 Message-ID: <13453.979259778@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/110 X-Sequence-Number: 771 What locale and encoding are you using? Evidently the LIKE index optimization is failing, but I would not have guessed that a string like 1:0: would cause a problem, especially not if all the entries in the column contain just digits and colons. You can find plenty of material about LIKE+index problems in the list archives. For 7.1, we've gone so far as to disable the optimization altogether in non-ASCII locales (and I'm sure we'll get complaints about that, too :-(). regards, tom lane