From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Marc Beneteau <mbeneteau(at)catgen(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: keyword (or fulltext) indexes, any planned developments? |
Date: | 2002-03-01 15:37:52 |
Message-ID: | 20020301233422.K5374-100000@houston.familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 26 Feb 2002, Marc Beneteau wrote:
B> Are there any plans to provide support for keyword indexes in Postgre?
The
> idea is to efficiently index every word in a long text column, in order to
> support queries such as :
There's nothing stopping you using fulltextindex, tsearch or OpenFTS.
> Select... from Products where ProductDescription like "%wool%" and
> ProductDescription like "%black%"
>
> This will work but it requires a table scan.
>
> I found an article in the contrib directory by Maarten Boekhold
> <maartenb(at)dutepp0(dot)et(dot)tudelft(dot)nl> (see below) , it's a good interim solution
> but it would be much more efficient if this functionality were built-in.
It wouldn't be any more efficient, really - just easier for the punters.
I use contrib/fulltextindex cos it's easy to set up (once you understand
it), and I have contributed some improvements to the code and
documentationfor 7.2 (letting you index more that one column in a table).
Remember, it's hard to give people choice if they can only use the
built-in indexing...
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | mlw | 2002-03-01 15:46:48 | Re: Database Caching |
Previous Message | Thomas T. Thai | 2002-03-01 15:27:17 | Re: keyword (or fulltext) indexes, any planned developments? |