| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Mark Dilger <pgsql(at)markdilger(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: text_position worst case runtime |
| Date: | 2006-05-19 16:45:22 |
| Message-ID: | 2197.1148057122@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jim C. Nasby" <jnasby(at)pervasive(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-05-19 16:54:55 | Re: text_position worst case runtime |
| Previous Message | Mike Ellsworth | 2006-05-19 16:42:49 | Re: [HACKERS] Toward A Positive Marketing Approach. |