Date: Fri, 27 Jun 2008 18:22:53 +0400 (MSD)
From: Oleg Bartunov <oleg@sai.msu.su>
To: Richard Huxton <dev@archonet.com>
cc: Bruce Momjian <bruce@momjian.us>, Marti Raudsepp <marti@juffo.org>,
	pgsql-www <pgsql-www@postgresql.org>
Subject: Re: No search results for "now"
In-Reply-To: <4864937E.8050602@archonet.com>
Message-ID: <Pine.LNX.4.64.0806271819390.11363@sn.sai.msu.ru>
References: <200806262235.m5QMZT109827@momjian.us>
	<4864937E.8050602@archonet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Fri, 27 Jun 2008, Richard Huxton wrote:

> Bruce Momjian wrote:
>> Marti Raudsepp wrote:
>>> Hi,
>>> 
>>> Someone pointed out in #postgresql that a search for "now" apparently
>>> gives no results, even though PostgreSQL has a now() function:
>>> http://search.postgresql.org/search?u=%2Fdocs%2F8.3%2Fstatic%2F&q=now
>>> 
>>> Probably needs to be fixed.
>> 
>> I can confirm this bug.  Anyone know the cause?
>
> Well, "now" is a stopword in the standard english configuration. Also "and", 
> "or", "if", "then" but not "C".

There was also problem with parser, reported several times.
Looks like it's a time to redo text search configuration at postgresql.org.


 	Regards,
 		Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83