Re: Search engine is not working - Mailing list pgsql-www

From Dave Page
Subject Re: Search engine is not working
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4A98B@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Search engine is not working  (Devrim GUNDUZ <devrim@gunduz.org>)
Responses Re: Search engine is not working
List pgsql-www

> -----Original Message-----
> From: pgsql-www-owner@postgresql.org
> [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Robert Treat
> Sent: 15 June 2004 14:24
> To: PostgreSQL WWW Mailing List
> Subject: Re: [pgsql-www] Search engine is not working
>
> On Tue, 2004-06-15 at 06:28, Devrim GUNDUZ wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> >
> > Hi,
> >
> > Interactive docs does not seem to be working. "Any" query
> returns no
> > result.
> >
> > Could someone please take a look at it?
> >
>
> When I search on "any" I get "Error in query: Only
> stopword(s) are used in query. You must specify at least one
> non-stop word" is that what you mean or something else?

A stop-word is one considered so common that searching for it is a
pointless waste of resources, thus it is ignored.

> btw, is now a bad time to post about a discrepancy between
> the search on www and the search on archives?  The following
> query looks for the word "weekly" in pgsql-announce list
> restricted to the last month:

That's because they're currently running on different backend databases.
The one on www is using John's server as the search daemon. The one on
archives is using search.postgresql.org (which just can't seem to keep
up with the indexing. It's on my todo list to move archives over to
John's box as well (which despite being on the end of a bit of a damp
piece of string somewhere in the Aussie outback, seems to work quite
well :-) )

/D

pgsql-www by date:

Previous
From: Devrim GUNDUZ
Date:
Subject: Re: Search engine is not working
Next
From: www@www.postgresql.com (World Wide Web Owner)
Date:
Subject: New News Entry