X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 548B9D1DB53 for ; Wed, 31 Mar 2004 01:07:27 +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 74720-03 for ; Tue, 30 Mar 2004 21:07:27 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id D538DD1DB0E for ; Tue, 30 Mar 2004 21:07:23 -0400 (AST) Received: from [63.195.55.98] (HELO 192.168.1.29) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4735956; Tue, 30 Mar 2004 17:08:45 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Palle Girgensohn , Tom Lane Subject: Re: LIKE should use index when condition doesn't include Date: Tue, 30 Mar 2004 17:06:54 -0800 User-Agent: KMail/1.5.4 Cc: pgsql-performance@postgresql.org References: <145170000.1080688008@palle.girgensohn.se> <200403301656.09664.josh@agliodbs.com> <173500000.1080695080@palle.girgensohn.se> In-Reply-To: <173500000.1080695080@palle.girgensohn.se> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403301706.54067.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/435 X-Sequence-Number: 6291 Palle, > Too bad... that was my idea, that it would somehow be aware that it is > equivalent to lower() like. It really is, isn't it? I would have though > they where synonymous. If not, makes ILIKE kind of unusable, at least > unless you're pretty certain the field will never indexed. Yup. I use it mostly for lookups in reference lists with < 100 items, where an index doesn't matter. -- -Josh Berkus Aglio Database Solutions San Francisco