Re: [ams@oryx.com: [ANNOUNCE] Archiveopteryx 1.10 released]
От | Dave Page |
---|---|
Тема | Re: [ams@oryx.com: [ANNOUNCE] Archiveopteryx 1.10 released] |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E40176CEC4@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Re: [ams@oryx.com: [ANNOUNCE] Archiveopteryx 1.10 released] ("Joshua D. Drake" <jd@commandprompt.com>) |
Ответы |
Re: [ams@oryx.com: [ANNOUNCE] Archiveopteryx 1.10
|
Список | pgsql-www |
> -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Joshua D. Drake > Sent: 19 September 2006 23:12 > To: Jim C. Nasby > Cc: pgsql-www@postgresql.org > Subject: Re: [pgsql-www] [ams@oryx.com: [ANNOUNCE] > Archiveopteryx 1.10 released] > > Jim C. Nasby wrote: > > So... since we all *love* the current archive engine (and > it's search) > > so much... > > > > What about switching over to this? It appears it should > work fine with > > majordomo, and I'd bet we could get someone from > Archiveopteryx to help > > with this. > > It also has a Tsearch2 interface :) Meaning what exactly? I'm sure any one of us is capable of writing a small script that could catch the mail messages from each list, and store them in a tsearch enabled database. The difficult bit is adding a good *web* interface to it with all the appropriate thread links and index pages, and without breaking all those pesky legacy URLs. There are also tens of thousands of documents in the search index that aren't emails that would also need to be handled. If you want to move to a new tsearch search engine (which I'm not against btw) then using our existing crawler script as a basis for a generic indexer would bypass all those problems, leaving just a web interface to tsearch to build. Regards, Dave.
В списке pgsql-www по дате отправления: