| From: | Teodor Sigaev <teodor(at)stack(dot)net> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tsearch thoughts |
| Date: | 2002-12-02 09:02:31 |
| Message-ID: | 3DEB21A7.6050201@stack.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I mean, when the index is created over the text column, instead of just
> indexing the text as-is, index the txt2txtidx'd version...?
For two reasons:
1. gist_txtidx_ops create with loss information (for less size), so any
operation with index must be checked
with original txtidx value. The way " REATE INDEX my_idx ON test USING
gist(txt2txtidx(a))" may decreas performance :(
2 OpenFTS. We wanted that txtidx works with OpenFTS. And adding dictionaries,
txt2txtidx, trigger, type mquery_txt etc
was an experiment.
--
Teodor Sigaev
teodor(at)stack(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lee Kindness | 2002-12-02 10:54:10 | 7.4 Wishlist |
| Previous Message | Tom Lane | 2002-12-02 07:02:27 | Re: toast table growing indefinitely? Known problems? |