Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id C77A69FB486 for ; Wed, 16 May 2007 11:42:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 33529-06 for ; Wed, 16 May 2007 11:42:09 -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.172]) by postgresql.org (Postfix) with ESMTP id A098B9FB483 for ; Wed, 16 May 2007 11:42:26 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id k3so100664ugf for ; Wed, 16 May 2007 07:42:24 -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=ErpJQ3OOGbahNfOPQ/zyzxcn/9cTx3chm149s4ozfI2ofFu1kPV/vI8VAGy7pwWeivx0QOE8L8JKM2EZ8RyzFyJdud/r7kh97G27Ye+Bkf9ik/K2y9cESg2XATZW4fVjyAmg50K/0z79RmXvrC1ucxX0qfp5dJaGzjthd1C7x2s= 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=N8wFJKig30NCrV8J7WuGTtS7DIUK+/SEPM8C1yeqtt0zwWubMtZeABCVa9Zsl7ErnWoLY9UUHaIupBkGaYk1/MR7KLlQ38g9PvskSsm3zVUUHDbbu7dpQQqXOFmufdcLhI1VShW7F/bzVkuBxLIGqwmGSxobFgaTZS2BPDkmWec= Received: by 10.67.88.20 with SMTP id q20mr6742339ugl.1179325945083; Wed, 16 May 2007 07:32:25 -0700 (PDT) Received: from ?172.24.32.118? ( [62.232.55.118]) by mx.google.com with ESMTP id a1sm17878164ugf.2007.05.16.07.32.22; Wed, 16 May 2007 07:32:22 -0700 (PDT) Message-ID: <464B15EF.4000808@enterprisedb.com> Date: Wed, 16 May 2007 15:32:15 +0100 From: Heikki Linnakangas User-Agent: Icedove 1.5.0.10 (X11/20070329) MIME-Version: 1.0 To: "Jim C. Nasby" CC: Bruce Momjian , PostgreSQL-patches Subject: Re: Maintaining cluster order on insert References: <200705152223.l4FMNJa17969@momjian.us> <464A33AB.1050401@enterprisedb.com> <20070516003810.GI20707@nasby.net> In-Reply-To: <20070516003810.GI20707@nasby.net> 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: 200705/239 X-Sequence-Number: 2339 Jim C. Nasby wrote: > What about adding the ability to ask the FSM for a page that's near a > given page? That way if you did have to go to the FSM you could at least > try and insert close to the page you originally wanted. Yeah, there's always room for improvement. I made the patch when I was working on clustered indexes, and was mostly concerned about getting inserts to the same page as other tuples with similar values so that the clustered index stays clustered. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com