Hmmm...thinking about it, maybe 'herring' is being reduced to 'her' after
the stemming process and hence is thought to be a stopword? This is a bug,
but how should it be fixed?
Although, tests don't support that:
usa=# select food_id, brand,description,ftiidx from food_foods where ftiidx
## 'himring';food_id | brand | description | ftiidx
---------+-------+-------------+--------
(0 rows)
usa=# select food_id, brand,description,ftiidx from food_foods where ftiidx
## 'hisring';food_id | brand | description | ftiidx
---------+-------+-------------+--------
(0 rows)
usa=# select food_id, brand,description,ftiidx from food_foods where ftiidx
## 'hising';food_id | brand | description | ftiidx
---------+-------+-------------+--------
(0 rows)
usa=# select food_id, brand,description,ftiidx from food_foods where ftiidx
## 'himing';food_id | brand | description | ftiidx
---------+-------+-------------+--------
(0 rows)
All work...?
Chris
> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Christopher
> Kings-Lynne
> Sent: Thursday, 5 September 2002 2:36 PM
> To: Hackers
> Subject: [HACKERS] contrib/tsearch
>
>
> Hi Oleg/Teodor,
>
> I'm sorry to keep posting bugs without patches, but I'm just
> hoping you guys
> know the answer faster than I...I know you're busy.
>
> What does tsearch have against the word 'herring' (as in the
> fish). Why is
> it considered a stopword?
>
> Attached is example queries...
>
> Chris
>
