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

From Tom Lane
Subject Re: text_position worst case runtime
Date
Msg-id 2197.1148057122@sss.pgh.pa.us
Whole thread Raw
In response to Re: text_position worst case runtime  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: text_position worst case runtime
List pgsql-hackers
"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.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [ADMIN] does wal archiving block the current client connection?
Next
From: Alvaro Herrera
Date:
Subject: Re: text_position worst case runtime