Re: Behaviour of to_tsquery(stopwords only)

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Behaviour of to_tsquery(stopwords only)
Date: 2008-03-06 17:21:46
Message-ID: 47D0282A.6030305@sigaev.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> => SELECT * FROM util.queries WHERE qid IN (195,248, 257, 332,
> 401,409,519,557,736,749,869,879,926) ORDER BY qid;
> qid | words | query
> -----+---------------------+----------
> 195 | can & of & tenders | 'tender' (3 clauses)
> 248 | tender & the & this | 'tender' (3 clauses)
> 257 | have & tender & for | 'tender' (3 clauses)
> 332 | for & tenders & of | 'tender' (3 clauses)
> 401 | tender & with | 'tender' (2 clauses)
> 409 | tenders & to | 'tender' (2 clauses)
> 519 | tender & to | 'tender' (2 clauses)
> 557 | tenders & be | 'tender' (2 clauses)
> 736 | tenderer | 'tender' (1 clause)
> 749 | tender | 'tender' (1 clause)
> 869 | tender | 'tender' (1 clause)
> 879 | tender | 'tender' (1 clause)
> 926 | tender | 'tender' (1 clause)
> (13 rows)
>
> So - is this a bug, feature, "feature"?

It's definitely a bug:
select count(*), query from queries group by query;
count | query
-------+----------
3 | 'tender'
4 | 'tender'
4 | 'tender'
(3 rows)

Will fix it soon.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-03-06 17:28:14 Re: Psql command-line completion bug
Previous Message Bruce Momjian 2008-03-06 17:19:45 Re: Some notes about the index-functions security vulnerability