On Thu, May 25, 2006 at 02:18:10PM -0300, Rodrigo Hjort wrote:
> make a index scan. Otherwise, i.e. using leading '%' on static text or bound
> paremeter, makes the planner always do a sequential scan. Is that the
I think more exactly, the planner can't possibly know how to plan an
indexscan with a leading '%', because it has nowhere to start.
Think of it this way: if you go to the public library, and say, "I
want a book. I can't remember its name exactly, but it starts with
'daytime'," you can find it by going to the title index and browsing
for things that start that way. If you go to the public library, and
say, "There's this book I want, but I can't remember the title. It's
red," you're going to have a lot of books to look through. Maybe all
If it were important enough -- say you left a $10,000 cheque inside
-- you might just start looking. Maybe you'll get lucky, and hit it.
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
I remember when computers were frustrating because they *did* exactly what
you told them to. That actually seems sort of quaint now.
In response to
pgsql-hackers by date
|Next:||From: Dave Cramer||Date: 2006-05-25 18:04:03|
|Subject: Re: LIKE, leading percent, bind parameters and indexes|
|Previous:||From: Marc G. Fournier||Date: 2006-05-25 17:39:22|
|Subject: Re: Gborg and pgfoundry|