Re: BUG #12204: Getting wrong results from full text search

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: prasanna(at)semantifi(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #12204: Getting wrong results from full text search
Date: 2014-12-11 19:46:50
Message-ID: 5817.1418327210@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> prasanna(at)semantifi(dot)com wrote:
>> select sckw.*
>> FROM semantified_content_key_word sckw
>> where TO_TSVECTOR(sckw.key_word_text) @@ TO_TSQUERY('exhausted');
>>
>> This is the query which i am running.And the keyword "exhausted" is present
>> only in one of the rows but i am getting all the 3 rows.

> My guess, without actual experimentation, is that "exhausted" stems down
> to "exhaust", which is present in the three provided rows.

Yeah. This is a feature, not a bug. If you don't want stemming to
happen, you should switch to a text search configuration that doesn't
do that. (I think the built-in "simple" configuration doesn't, but
in any case you could certainly construct one that doesn't.)

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-12-11 19:49:40 Re: BUG #12203: No password dialog when access the postgresql server
Previous Message Matt Freeman 2014-12-11 18:17:51 Re: BUG #12202: json operator ->>with offset