Re: text_position worst case runtime
| От | Alvaro Herrera |
|---|---|
| Тема | Re: text_position worst case runtime |
| Дата | |
| Msg-id | 20060519165455.GH9919@surnet.cl обсуждение исходный текст |
| Ответ на | Re: text_position worst case runtime (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: text_position worst case runtime
|
| Список | 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 по дате отправления: