Re: Worthwhile optimisation of position()? - Mailing list pgsql-hackers

From Tim Allen
Subject Re: Worthwhile optimisation of position()?
Date
Msg-id 442393D5.1020505@proximity.com.au
Whole thread Raw
In response to Re: Worthwhile optimisation of position()?  (Thomas Hallgren <thomas@tada.se>)
Responses Re: Worthwhile optimisation of position()?
List pgsql-hackers
Thomas Hallgren wrote:
> Christopher Kings-Lynne wrote:
> 
>> Is it worth allowing this:
>>
>> select count(*) from users_users where position('ch' in username) = 0;
>>
>> To be able to use an index, like:
>>
>> select count(*) from users_users where username like 'ch%';
>>
>> At the moment the position() syntax will do a seqscan, but the like 
>> syntax will use an index.
>>
> You must compare position('ch' in username) to '%ch%' instead of 'ch%' 
> in this respect.
> 
> The position function must look for 'ch' everywhere in the string so 
> there's no way it can use an index.

I think the '= 0' bit is what Chris was suggesting could be the basis 
for an optimisation.

Tim

-- 
-----------------------------------------------
Tim Allen          tim@proximity.com.au
Proximity Pty Ltd  http://www.proximity.com.au/


pgsql-hackers by date:

Previous
From: Thomas Hallgren
Date:
Subject: Re: Worthwhile optimisation of position()?
Next
From: Tom Lane
Date:
Subject: Re: Worthwhile optimisation of position()?