X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 09119D9007; Wed, 16 Nov 2005 21:34:25 -0400 (AST) 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 84452-06; Thu, 17 Nov 2005 01:34:28 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from houston.familyhealth.com.au (houston.au.fhnetwork.com [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id 1F329D8D8F; Wed, 16 Nov 2005 21:34:23 -0400 (AST) Received: from houston.familyhealth.com.au (localhost [127.0.0.1]) by houston.familyhealth.com.au (Postfix) with ESMTP id 8803625077; Thu, 17 Nov 2005 09:34:26 +0800 (WST) Received: from [127.0.0.1] (work-40.internal [192.168.0.40]) by houston.familyhealth.com.au (Postfix) with ESMTP id 61F9F2507D; Thu, 17 Nov 2005 09:34:25 +0800 (WST) Message-ID: <437BDF22.9030109@familyhealth.com.au> Date: Thu, 17 Nov 2005 09:38:42 +0800 From: Christopher Kings-Lynne User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Simon Riggs Cc: pgsql-www@postgresql.org, Tom Lane , Steve Wampler , Postgres-performance Subject: Re: [PERFORM] Help speeding up delete References: <43790A99.9050603@noao.edu> <4162.1132011763@sss.pgh.pa.us> <1132171206.4959.60.camel@localhost.localdomain> In-Reply-To: <1132171206.4959.60.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-familyhealth-MailScanner-Information: Please contact the ISP for more information X-familyhealth-MailScanner: Found to be clean X-familyhealth-MailScanner-From: chriskl@familyhealth.com.au X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.037 required=5 tests=[AWL=0.037] X-Spam-Score: 0.037 X-Spam-Level: X-Archive-Number: 200511/106 X-Sequence-Number: 8821 >>Update to 7.4 or later ;-) >> >>Quite seriously, if you're still using 7.2.4 for production purposes >>you could justifiably be accused of negligence. There are three or four >>data-loss-grade bugs fixed in the later 7.2.x releases, not to mention >>security holes; and that was before we abandoned support for 7.2. >>You *really* need to be thinking about an update. > > > Perhaps we should put a link on the home page underneath LATEST RELEASEs > saying > 7.2: de-supported > > with a link to a scary note along the lines of the above. I strongly support an explicit desupported notice for 7.2 and below on the website... Chris