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 6BEDC9FA27F for ; Sun, 16 Jul 2006 15:43:20 -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 43253-02 for ; Sun, 16 Jul 2006 15:43:10 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 849949FA21D for ; Sun, 16 Jul 2006 15:43:11 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6GIh9AD020439 for ; Sun, 16 Jul 2006 14:43:09 -0400 (EDT) To: pgsql-www@postgreSQL.org Subject: Mail archive indexes are broken, URLs too Date: Sun, 16 Jul 2006 14:43:09 -0400 Message-ID: <20438.1153075389@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/62 X-Sequence-Number: 10295 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. regards, tom lane