X-Original-To: pgsql-www-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 958549FA21D for ; Sun, 16 Jul 2006 16:43:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 73847-03 for ; Sun, 16 Jul 2006 19:43:45 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from hub.org (hub.org [200.46.204.220]) by postgresql.org (Postfix) with ESMTP id 4A7559F95E3 for ; Sun, 16 Jul 2006 16:43:46 -0300 (ADT) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 94266290C6B for ; Sun, 16 Jul 2006 16:43:42 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 72556-06; Sun, 16 Jul 2006 19:43:42 +0000 (UTC) Received: from ganymede.hub.org (blk-224-179-167.eastlink.ca [24.224.179.167]) by hub.org (Postfix) with ESMTP id 0233B290C38; Sun, 16 Jul 2006 16:43:40 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id C4D3849D09; Sun, 16 Jul 2006 16:43:43 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id BEADA49CB2; Sun, 16 Jul 2006 16:43:43 -0300 (ADT) Date: Sun, 16 Jul 2006 16:43:43 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Tom Lane cc: pgsql-www@postgreSQL.org Subject: Re: Mail archive indexes are broken, URLs too In-Reply-To: <20438.1153075389@sss.pgh.pa.us> Message-ID: <20060716164208.Q957@ganymede.hub.org> References: <20438.1153075389@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/67 X-Sequence-Number: 10300 On Sun, 16 Jul 2006, 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. Nope, for one simple reason ... if, for some reason, at some point in the future, we have to regenerate everything anyway (ie. the last time we did a major template change for the archives), all the #'ng is going to end up reverting back to what it is now ... so we'd only be 'delaying the inevitable' ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664