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 8E1109FA4E3; Wed, 19 Jul 2006 16:31:06 -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 52347-10; Wed, 19 Jul 2006 16:30:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id CED049FA4AE; Wed, 19 Jul 2006 16:30:57 -0300 (ADT) Received: from [192.168.1.137] (rrcs-24-173-98-157.sw.biz.rr.com [24.173.98.157]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by noel.decibel.org (Postfix) with ESMTP id 93D0256431; Wed, 19 Jul 2006 14:30:56 -0500 (CDT) In-Reply-To: <20060716164208.Q957@ganymede.hub.org> References: <20438.1153075389@sss.pgh.pa.us> <20060716164208.Q957@ganymede.hub.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: Tom Lane , pgsql-www@postgreSQL.org Content-Transfer-Encoding: 7bit From: Jim Nasby Subject: Re: Mail archive indexes are broken, URLs too Date: Wed, 19 Jul 2006 13:12:06 -0500 To: Marc G. Fournier X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/89 X-Sequence-Number: 10322 On Jul 16, 2006, at 2:43 PM, Marc G. Fournier wrote: > 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' ... This is a problem for most mailing lists, but I think it's a critical one for us since we depend very, very heavily on the archives. Can we change the lists so that they will generate a UUID and add it to message headers, and then allow the archive software to key off of that? -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461