Re: Worthwhile optimisation of position()?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tim Allen <tim(at)proximity(dot)com(dot)au>
Cc: Thomas Hallgren <thomas(at)tada(dot)se>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Worthwhile optimisation of position()?
Date: 2006-03-24 06:48:18
Message-ID: 28782.1143182898@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tim Allen <tim(at)proximity(dot)com(dot)au> writes:
> Thomas Hallgren wrote:
>> 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.

Yeah. AFAICS the transformation Chris suggested is valid. I'm really
dubious that it's worth expending planner cycles to look for it though.
LIKE is something that everybody and his brother uses, but who uses this
position()=0 locution?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Hallgren 2006-03-24 06:51:57 Re: Worthwhile optimisation of position()?
Previous Message Tim Allen 2006-03-24 06:38:13 Re: Worthwhile optimisation of position()?