From: Josh Berkus <josh@agliodbs.com>
To: Palle Girgensohn <girgen@pingpong.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: LIKE should use index when condition doesn't include
Date: Tue, 30 Mar 2004 17:06:54 -0800
Message-ID: <200403301706.54067.josh@agliodbs.com> (raw)
In-Reply-To: <173500000.1080695080@palle.girgensohn.se>
References: <145170000.1080688008@palle.girgensohn.se>
<200403301656.09664.josh@agliodbs.com>
<173500000.1080695080@palle.girgensohn.se>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, girgen@pingpong.net, tgl@sss.pgh.pa.us
Subject: Re: LIKE should use index when condition doesn't include
In-Reply-To: <200403301706.54067.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox