X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BDEDE5E48F9 for ; Sun, 5 Sep 2004 08:49:36 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 42728-01 for ; Sun, 5 Sep 2004 07:49:29 +0000 (GMT) Received: from ra.sai.msu.su (ra.sai.msu.su [158.250.29.2]) by svr1.postgresql.org (Postfix) with ESMTP id E9BD05E40BA for ; Sun, 5 Sep 2004 08:49:17 +0100 (BST) Received: from ra (ra [158.250.29.2]) by ra.sai.msu.su (8.12.10/8.12.10) with ESMTP id i857n6QT015593; Sun, 5 Sep 2004 11:49:06 +0400 (MSD) Date: Sun, 5 Sep 2004 11:49:06 +0400 (MSD) From: Oleg Bartunov X-X-Sender: megera@ra.sai.msu.su To: John Hansen Cc: Greg Sabino Mullane , pgsql-www@postgresql.org Subject: Re: Suggestion for improving Archives In-Reply-To: <5066E5A966339E42AA04BA10BA706AE5618E@rodrick.geeknet.com.au> Message-ID: References: <5066E5A966339E42AA04BA10BA706AE5618E@rodrick.geeknet.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/40 X-Sequence-Number: 5110 On Sun, 5 Sep 2004, John Hansen wrote: > > While we are here, the "for files modified" bit of > > the search.postgresql.org box does not seem to work: > > searching for "nested transactions vadim" brings back 62 > > hits, regardless of whether I set it to within one day or > > within 2 years. The top hit is from June 2000. There is also > > no way to sort it by date, which can be extremely important. > > The ads on every page are annoying as well. > > > > Seems to fork fine for me, no results in the last 3 months,5 in the last > 6 and 12, 26 in the last 2 years. Sorting by date, rather than > relevance, could be added. > Marc again dropped last time modification header, so it's impossible to sort results by date (in general case ) without specific parser. Also, he changed template for message. These changes cause recrawling the whole archive each time and overloading archives.postgresql.org More specific search engine could use another source of information which messages to crawl, but one we use at pgsql.ru is a general search engine and it can't get modification date without proper header. I suggest: 1. Use 3-server architecture (image server, frontend, backend) which could be reduced to 2 servers (image+frontend, backend) - frontend could be plain apache+mod_accel and serve/cache all backends outputs, backend is a modperl or/and php enabled apache. 2. return last modification header - be friendly to crawlers and browsers 3. stop changing message template Oleg > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > Regards, Oleg _____________________________________________________________ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83