Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id A8F0D9FB672 for ; Tue, 10 Jul 2007 08:44:02 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 30024-06-2 for ; Tue, 10 Jul 2007 08:43:59 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by postgresql.org (Postfix) with ESMTP id DAA0E9FB5F1 for ; Tue, 10 Jul 2007 08:43:58 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id a2so1410491ugf for ; Tue, 10 Jul 2007 04:43:57 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=q/LXJIyeFXzjdCNxr+kKMmYkpgmM+Mh3jXDn0pbY0HOlY3Zn4/M4lvyEHiDs7H1nfLTuaEetqxBq+QFkjktIT8if99dl6S+caMjJSQXMESZ1VgVhW6Qfwgr2CMXz9JDLtSLsyos/9zjxJLuYUgUY/fU0RyburM7FkUvCuaSLJJ8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=qyol4RO63oWPNwEQxr4+JLn64845xlLALPdf7GyZfFS+LeMWljQ4IJ2HxVEdB/Pce18UEvyHbhqfl5h82c4EukqhCacxUmOCK4BQpI2132xGT19tzSKgASgYX2Hd1MazxcwTYvytuec46iVQjZJSkQpNFgPDjYntxtiM7S4MxGY= Received: by 10.66.242.19 with SMTP id p19mr5870056ugh.1184067837039; Tue, 10 Jul 2007 04:43:57 -0700 (PDT) Received: from ?172.24.32.84? ( [62.232.55.118]) by mx.google.com with ESMTPS id m1sm3867935uge.2007.07.10.04.43.53 (version=SSLv3 cipher=RC4-MD5); Tue, 10 Jul 2007 04:43:54 -0700 (PDT) Message-ID: <469370CA.1060608@enterprisedb.com> Date: Tue, 10 Jul 2007 12:43:06 +0100 From: Heikki Linnakangas User-Agent: Icedove 1.5.0.10 (X11/20070329) MIME-Version: 1.0 To: Gregory Stark CC: Tom Lane , Jaime Casanova , "Jim C. Nasby" , Bruce Momjian , PostgreSQL-patches Subject: Re: Maintaining cluster order on insert References: <200705152223.l4FMNJa17969@momjian.us><464A33AB.1050401@enterprisedb.com> <20070516003810.GI20707@nasby.net><464B15EF.4000808@enterprisedb.com><464D96D6.1030608@enterprisedb.com> <457.1184023772@sss.pgh.pa.us> <87odikzems.fsf@oxford.xeocode.com> In-Reply-To: <87odikzems.fsf@oxford.xeocode.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/126 X-Sequence-Number: 3124 Gregory Stark wrote: > It's pretty serious what you're suggesting since it means that we'll basically > never have a real cluster feature. I would sure hope we're missing something > and there's a way to make this work usefully. Another approach would be an online CLUSTER command. That means there'll be a lot of churn when tuples need to be moved back and forth, along with updating indexes, but it'd take the overhead out of the critical path. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com