| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Michael Paesold" <mpaesold(at)gmx(dot)at>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Mike Rylander" <mrylander(at)gmail(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: tsearch2 in PostgreSQL 8.3? |
| Date: | 2007-08-16 16:10:54 |
| Message-ID: | 87eji3v4s1.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Yeah, unfortunately we overlooked the implications of the conversion to
> tsvector being environment-dependent. Those opclasses will have to go
> away again. AFAICS the only safe way to build an index directly on a
> text column is
>
> CREATE INDEX idxname ON tblname USING gin (to_tsvector('config', textcolumn));
Is there a null configuration which could be the default for the casts? So the
syntax would still work and would generate an index which worked well but has
no stop words, no stemming, etc?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-08-16 16:12:02 | Re: build farm failures |
| Previous Message | Decibel! | 2007-08-16 15:50:36 | Re: Deferred Constraints |