Re: text_position worst case runtime

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Mark Dilger <pgsql(at)markdilger(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: text_position worst case runtime
Date: 2006-05-19 17:08:11
Message-ID: 2399.1148058491@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> You've obviously missed the point of my concern, which is code bloat.

> 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.

And how much code would those take? The bottom line here is that we
don't have a pile of complaints about the performance of text_position,
so it's difficult to justify making it much more complicated than it
is now.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc Munro 2006-05-19 17:14:50 Re: [pgsql-hackers] Daily digest v1.5943 (21 messages)
Previous Message Josh Berkus 2006-05-19 17:05:59 Re: New feature proposal