Re: Postgresql.org search engine.

> -----Original Message-----
> From: Oleg Bartunov [mailto:oleg(at)sai(dot)msu(dot)su]
> Sent: 30 January 2004 19:06
> To: Dave Page
> Cc: josh(at)agliodbs(dot)com; pgsql-www(at)postgresql(dot)org
> Subject: Re: [pgsql-www] Postgresql.org search engine.
>
>
> Guys, there is a big difference between semi-static index
> (aspseek) and incremental indexing of incoming documents
> (tsearch2). Our approach is to develop fully automatical
> searchable mailing list archive with instant indexing. So,
> for example, I see my postings about subj.
> already in database and *searchable* ! I don't expect
> aspseek's search engine at postgresql.org has my recent
> postings in its index.

No it doesn't, but it probably could do with a little clever scripting
to expire the right index pages before each run.

In addition, one of the mods made in the version we are using is the
addition of an XML feed to the indexer - John (the guy responsible for
the port) is keen for me to use this for far more efficient indexing of
the archives, however I have yet to do this mainly because it requires
hacking mhonarc about to output the XML data.

> OpenFTS has full access to metadata of documents, so we could
> limit search '
> range by date, by list, by authors, so smart user could get
> reasonable search performance (relevance is very good,
> because it based on proximity). So, different searches for
> different purposes !

We don't have those fields, but the XML feed was originally written for
indexing data from online catalogues and has added fields like price.
I'd be surprised if others couldn't be added as well.

Regards, Dave.