Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 3AC6B9FB5AF for ; Sat, 16 Jun 2007 01:48:50 -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 05305-05 for ; Sat, 16 Jun 2007 01:48:45 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by postgresql.org (Postfix) with ESMTP id 0B8C79FB425 for ; Sat, 16 Jun 2007 01:48:46 -0300 (ADT) Received: by an-out-0708.google.com with SMTP id c36so233157ana for ; Fri, 15 Jun 2007 21:48:46 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NKl2OU1Jkh1KxbxSMrTawpeIXgt5BYiIfTa3ghVPu2zwYpO0fTF5+BabNxaCWuTaZv5yhDomqb1iMOTWF2t4/onWo/SmOYVg7apcI8R7kfmURP7AbeByAsvfS7s2lIUvx/uCJH11Q2JvzjtpC122WK8/U8Ah8836NojgZrvbcOw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=L70TGq9cbpk0RfdcCI7wHvNU1DpQlsqbwSLlwaj6AuDlqFjgTEKLWKZn0dYNXnwj6Sdhf/Mzx1se3vzN55p+35UCGmGz0ZYLmmu8j22W/ciBoJ57SR1q2rOAVck9W/FG3yOhQijXkBBDg7UaAud5WhFFKgPCx9JvngS56X34NvM= Received: by 10.100.94.3 with SMTP id r3mr318457anb.1181969326444; Fri, 15 Jun 2007 21:48:46 -0700 (PDT) Received: by 10.100.45.15 with HTTP; Fri, 15 Jun 2007 21:48:46 -0700 (PDT) Message-ID: Date: Sat, 16 Jun 2007 04:48:46 +0000 From: "Jaime Casanova" To: "Jim C. Nasby" Subject: Re: Maintaining cluster order on insert Cc: "Heikki Linnakangas" , "Pavan Deolasee" , PostgreSQL-patches In-Reply-To: <20070527190136.GR92628@nasby.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <464A33AB.1050401@enterprisedb.com> <464B15EF.4000808@enterprisedb.com> <464D96D6.1030608@enterprisedb.com> <464F410C.8090900@enterprisedb.com> <2e78013d0705210117y6a65245cw426bbaafa9eb6419@mail.gmail.com> <2e78013d0705210232m5d031a6fk779be6d7df5a2e3c@mail.gmail.com> <46516B0B.3000907@enterprisedb.com> <20070527190136.GR92628@nasby.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/159 X-Sequence-Number: 2775 On 5/27/07, Jim C. Nasby wrote: > On Mon, May 21, 2007 at 10:48:59AM +0100, Heikki Linnakangas wrote: > > > > IOW it's working as designed. But maybe it's not the desired behavior. > > Should we have a special case and always respect the fillfactor when > > inserting to the last page of the heap? > > I think that would be following with least surprise. What's the status of this patch? are we waiting an update? AFAIU, it's not fair to say that the patch maintain cluster order... it just try to keep similar rows on the same page if possible (it's not the same thing)... if it can't then it simply insert at the last page as usual but we have wasted time in the try... so the real question is if there is any performance win on this... have you some numbers? another question: if the fillfactor is 100% then is a complete waste of time to look for a suggested block. maybe we could check for that? -- regards, Jaime Casanova "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs and the universe trying to produce bigger and better idiots. So far, the universe is winning." Richard Cook