From: | Sushant Sinha <sushant354(at)gmail(dot)com> |
---|---|
To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: phrase search |
Date: | 2008-06-04 02:49:44 |
Message-ID: | 1212547785.7018.5.camel@dragflick |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2008-06-03 at 22:16 +0400, Teodor Sigaev wrote:
> > This is far more complicated than I thought.
> >> Of course, phrase search should be able to use indexes.
> > I can probably look into how to use index. Any pointers on this?
>
> src/backend/utils/adt/tsginidx.c, if you invent operation # in tsquery then you
> will have index support with minimal effort.
> >
> > Yes this is exactly how I am using in my application. Do you think this
> > will solve a lot of common case or we should try to get phrase search
>
> Yeah, it solves a lot of useful case, for simple use it's needed to invent
> function similar to existsing plaitnto_tsquery, say phraseto_tsquery. It should
> produce correct tsquery with described above operations.
>
I can add index support and support for arbitrary distance between
lexeme.
It appears to me that supporting arbitrary boolean expression will be
complicated. Can we pull out something from TSQuery?
-Sushant.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2008-06-04 03:20:11 | Re: Core team statement on replication in PostgreSQL |
Previous Message | Robert Treat | 2008-06-04 02:24:37 | Re: rfc: add pg_dump options to dump output |