Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id A59E69FB36A for ; Sun, 27 May 2007 15:27:36 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 24667-01 for ; Sun, 27 May 2007 15:27:31 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by postgresql.org (Postfix) with ESMTP id 186709FB36C for ; Sun, 27 May 2007 15:27:32 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id u2so727527uge for ; Sun, 27 May 2007 11:27:31 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Kh6tVlFfICjqsa2YZS1btGoHGOvC8IQhdUiMLZOVigbCJg873eVLp4iSboGso5iAKRVakdFY+0QPBmZOgVbrrvmzXguYZLXTvIgIJ4s+sL8Q/WWezJAGh5EqEIf5VZo578WCSAcN/3HfnTDuB2srGiCw2YUAseTw8z+YS+b4sm4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=L2Fl9n3P1mIRMhbV0A/0SFZcLZLI0GFeqzfnl1fICb/FVniPohjouUHkOV+azaOOD3AGScrj4OKNGq9rBOsQ0okX3EfHF9sr4mXud4Q3ys7rtsFzinMvcyxzBrYdPxGbwGMoHcCBgN1Cko4py7s44S9yGkz0vPLrFTHDcGWCtfc= Received: by 10.78.142.14 with SMTP id p14mr1471420hud.1180290451683; Sun, 27 May 2007 11:27:31 -0700 (PDT) Received: by 10.78.145.14 with HTTP; Sun, 27 May 2007 11:27:31 -0700 (PDT) Message-ID: <88daf38c0705271127x3fb1e83cp7d42e417cf046840@mail.gmail.com> Date: Sun, 27 May 2007 20:27:31 +0200 From: "Alexander Staubo" To: PFC Subject: Re: Feature suggestion : FAST CLUSTER Cc: "Jim C. Nasby" , "pgsql-performance@postgresql.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070527155338.GM92628@nasby.net> X-Google-Sender-Auth: dec3e1dc95ca93b1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/566 X-Sequence-Number: 24956 On 5/27/07, PFC wrote: > PostgreSQL humiliates InnoDB on CPU-bound workloads (about 2x faster > since I run it on dual core ; InnoDB uses only one core). However, InnoDB > can automatically cluster tables without maintenance. How does it know what to cluster by? Does it gather statistics about query patterns on which it can decide an optimal clustering, or does it merely follow a clustering previously set up by the user? Alexander.