Personally I'd like to see effort go into getting fts.postgresql.org
back up and going; I've always had better results searching their.
Robert Treat
On Thu, 2003-09-04 at 14:38, Marc G. Fournier wrote:
>
> k, try the search engine now ... I just found a 'missing index' on one of
> the critical tables, and I'm getting more realistic speeds on search
> results ...
>
> On Thu, 4 Sep 2003, Marc G. Fournier wrote:
>
> >
> > go for it, point it at archives.postgresql.org though, since that is the
> > major part of the search engine
> >
> > On Thu, 4 Sep 2003, scott.marlowe wrote:
> >
> > > On Tue, 2 Sep 2003, Marc G. Fournier wrote:
> > >
> > > >
> > > > okay, first off ... what URL? I've been working on, and testing, archives
> > > > all week, and altho getting things down below a 2min search appears to be
> > > > near impossible (anyone know something *better* then mnogosearch that will
> > > > handle >250k URLs and growing ... ? we tried ht/Dig before, and the
> > > > resources it suck'd were outrageous) ...
> > >
> > > Hi Marc, I use htdig at work to index a rather large web site and it
> > > doesn't use resources all that bad. My htdig db directory is only 250
> > > megs and it screams. Are you sure it was that bad?
> > >
> > > Would it be ok if I pointed a test instance of htdig at postgresql.org at
> > > night and indexed it to get an idea of how much space it'll take to index
> > > it? I'm a huge fan of htdig/ warts and all, so I'd kinda like to see if
> > > it can be made to work.
> > >
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
