From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | jerome(dot)eteve(at)gmail(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: What is the simpliest text search configuration? |
Date: | 2009-11-12 15:20:33 |
Message-ID: | 24528.1258039233@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
=?UTF-8?B?SsOpcsO0bWUgRXTDqXbDqQ==?= <jerome(dot)eteve(at)gmail(dot)com> writes:
> I'd like to implement a full text search with postgresql, and I can't find
> a text search configuration that would just:
> map unicode accentuated letters to an un-accentuated equivalent
> tokenize the words (and skip any non word characters)
> no stopwords
> lower case the tokens
> How can I achieve this? I'm particularly interested in deactivating
> the stopwords filtering.
> I tried pg_catalog.simple, but despite its name, it still considers stop words.
What's wrong with specifying an empty stopword list?
(To me, removing accents is already past what I'd expect of a "simple"
configuration, so I doubt you're going to find a dictionary that
provides exactly that set of features and no other ones.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2009-11-12 16:24:03 | Re: What is the simpliest text search configuration? |
Previous Message | Tom Lane | 2009-11-12 15:00:29 | Re: knowing which table/schema is going to be chosen |