X-Original-To: pgsql-www-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A83A79FB1E3 for ; Tue, 1 Aug 2006 16:11:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 16720-08 for ; Tue, 1 Aug 2006 16:11:26 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 2B4D09FB1C3 for ; Tue, 1 Aug 2006 16:11:25 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id k71JBQl12986; Tue, 1 Aug 2006 15:11:26 -0400 (EDT) From: Bruce Momjian Message-Id: <200608011911.k71JBQl12986@momjian.us> Subject: Re: Mail archive indexes are broken, URLs too In-Reply-To: <200607291539.k6TFd0B14602@momjian.us> To: PostgreSQL www Date: Tue, 1 Aug 2006 15:11:26 -0400 (EDT) CC: Tom Lane , "Marc G. Fournier" X-Mailer: ELM [version 2.4ME+ PL122k (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.075 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/1 X-Sequence-Number: 10392 Is anyone working on this? Marc? If not, who can make these modifications to the archive numbering? --------------------------------------------------------------------------- Bruce Momjian wrote: > Tom Lane wrote: > > When Marc fixed the message-boundary pattern and regenerated the > > archives, many of the existing messages changed URLs because they > > got assigned slightly different numbers. I notice that the archive > > search engine hasn't yet tracked this change --- if you do a search > > and click on a link to a message, you'll arrive at a message close > > to the one you want but probably not quite it. > > > > Regenerating the archive indexes is presumably not hard, but there's > > a bigger problem: for awhile now many of us have been in the habit > > of citing old discussions by archive URLs. All those links are now > > broken too, and I can't think of any easy way to fix them. And then > > there's Google etc. > > > > I wonder if it'd be better to revert the regeneration of the archives, > > and only apply the new message-boundary pattern to future messages. > > Agreed. There have been no changes since we discussed this. > > The best proposal was to renumber the newly-found items to the end of > the numeric range for the pre-July 2006 archives, and to properly number > July 2006 and later archives. And this date range has to be enbedded in > the archive script so if it is ever run again, this behavior continues > to happen. > > The longer we take to fix this, the more likely that people are creating > URL's that refer to the existing pre-July 2006 numbering which should > change. It needs to be fixed quickly. > > And we can't just leave it alone because old archive emails have URLs > that point to now-incorrect numbers, and there is no good way to fix > that everywhere are emails are archived. > > -- > Bruce Momjian bruce@momjian.us > EnterpriseDB http://www.enterprisedb.com > > + If your life is a hard drive, Christ can be your backup. + > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +