| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Markus Schiltknecht <markus(at)bluegap(dot)ch>, Pavel Stehule <pavel(dot)stehule(at)hotmail(dot)com>, teodor(at)sigaev(dot)ru |
| Subject: | Re: tsearch in core patch, for inclusion |
| Date: | 2007-02-23 10:13:38 |
| Message-ID: | 200702231113.39016.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Donnerstag, 22. Februar 2007 18:07 schrieb Markus Schiltknecht:
> > I agree so enhancing parser oabout not standard construct isn't good.
>
> Generally? Wow! This would mean PostgreSQL would always lack behind
> other RDBSes, regarding ease of use. Please don't do that!
You are confusing making a full-text index and configuring the full-text
engine. Tsearch already gives you a standard CREATE INDEX variant to do the
former. The discussion here is about the latter, and notably Oracle uses
functions there.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-02-23 10:15:22 | Re: tsearch in core patch, for inclusion |
| Previous Message | Guillaume Smet | 2007-02-23 10:00:41 | Re: Simple Column reordering |