X-Original-To: pgsql-performance@postgresql.org Received: from houston.familyhealth.com.au (unknown [203.59.48.253]) by postgresql.org (Postfix) with ESMTP id A55E5475F09 for ; Mon, 17 Mar 2003 20:34:33 -0500 (EST) Received: (from root@localhost) by houston.familyhealth.com.au (8.11.6/8.11.6) id h2I1Yac95711 for pgsql-performance@postgresql.org; Tue, 18 Mar 2003 09:34:36 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Received: from mariner (mariner.internal [192.168.0.101]) by houston.familyhealth.com.au (8.11.6/8.9.3) with SMTP id h2I1YW795594; Tue, 18 Mar 2003 09:34:32 +0800 (WST) Message-ID: <07b501c2ecee$8917b8c0$6500a8c0@fhp.internal> From: "Christopher Kings-Lynne" To: "Kendrick C. Wilson" , References: Subject: Re: postgresql meltdown on PlanetMath.org Date: Tue, 18 Mar 2003 09:34:36 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-scanner: scanned by Inflex 0.1.5c - (http://www.inflex.co.za/) X-Archive-Number: 200303/128 X-Sequence-Number: 1426 > What is the structure of you table? > Is the data types in the table the same as in the SQL.... > > Did you create the index after the loading the table? > cluster the table around the most used index.... There is no point clustering a table around the most used index, unless access to the index is non-random. eg. you are picking up more than one consecutive entry from the index at a time. eg. Indexes on foreign keys are excellent for clustering. Chris