| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | PFC <lists(at)peufeu(dot)com> |
| Cc: | mark(at)mark(dot)mielke(dot)cc, Mark Lewis <mark(dot)lewis(at)mir3(dot)com>, James Mansion <james(at)mansionfamily(dot)plus(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Alexander Staubo <alex(at)purefiction(dot)net>, Andy <frum(at)ar-sd(dot)net>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: LIKE search and performance |
| Date: | 2007-05-25 17:08:53 |
| Message-ID: | 46571825.30707@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
PFC wrote:
>
>> OK - any application that allows user-built queries: <choose column:
>> foo> <choose filter: contains> <choose target: "bar">
>>
>> Want another? Any application that has a "search by name" box - users
>> can (and do) put one letter in and hit enter.
>>
>> Unfortunately you don't always have control over the selectivity of
>> queries issued.
>
> -*- HOW TO MAKE A SEARCH FORM -*-
>
> Imagine you have to code the search on IMDB.
>
> This is what a smart developer would do
All good domain-specific tips to provide users with a satisfying
search-experience.
None of which address the question of what plan PG should produce for:
SELECT * FROM bigtable WHERE foo LIKE 's%'
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arnau | 2007-05-25 17:16:05 | Re: How PostgreSQL handles multiple DDBB instances? |
| Previous Message | Joshua D. Drake | 2007-05-25 17:06:46 | Re: LIKE search and performance |