Poorly designed tsearch NOTICEs - Mailing list pgsql-hackers

From Tom Lane
Subject Poorly designed tsearch NOTICEs
Date
Msg-id 11978.1192908297@sss.pgh.pa.us
Whole thread Raw
Responses Re: Poorly designed tsearch NOTICEs
List pgsql-hackers
regression=# SELECT plainto_tsquery('the any'); 
NOTICE:  query contains only stopword(s) or doesn't contain lexeme(s), ignoredplainto_tsquery 
-----------------
(1 row)

regression=# select ''::tsquery;
NOTICE:  tsearch query doesn't contain lexeme(s): ""tsquery 
---------
(1 row)

IMHO, it's really bad design to have this sort of NOTICE emitted by
tsquery input.  Even if an application uses numnode() or querytree() or
something similar to detect bogus queries, it's going to have its logs
cluttered with these notices.

I could see having the @@ operator emit the notice if the query is
actually used for searching --- though I'm not quite sure how to get it
to come out only once per query ... maybe we could put it into the index
consistent() functions somehow?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Sibte Abbas"
Date:
Subject: Re: NULL and plpgsql rows
Next
From: Bruce Momjian
Date:
Subject: MVCC, undo log, and HOT