Re: text_position worst case runtime - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: text_position worst case runtime
Date
Msg-id 20060519165455.GH9919@surnet.cl
Whole thread Raw
In response to Re: text_position worst case runtime  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: text_position worst case runtime
List pgsql-hackers
Tom Lane wrote:
> "Jim C. Nasby" <jnasby@pervasive.com> writes:
> > Perhaps it would be best to add a seperate set of functions that use
> > boyer-moore, and reference them in appropriate places in the
> > documentation. Unless someone has a better idea on how we can find out
> > what people are actually doing in the field...
> 
> You've obviously missed the point of my concern, which is code bloat.
> A parallel set of functions incorporating B-M would make things worse
> not better from that standpoint.  (Unless you are proposing that someone
> do it as a separate pgfoundry project; which'd be fine with me.  I'm
> just concerned about how much we buy into as core features.)

So why not just replace our code with better algorithms?  We could use
Shift-Or or Shift-And which AFAIK are even better than Boyer-Moore.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: text_position worst case runtime
Next
From: Marc Munro
Date:
Subject: Re: New feature proposal