X-Original-To: pgsql-performance@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 28063476375 for ; Fri, 25 Apr 2003 16:10:51 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 2F597476350 for ; Fri, 25 Apr 2003 16:10:50 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h3PKAlU6029561; Fri, 25 Apr 2003 16:10:49 -0400 (EDT) To: Hannu Krosing Cc: jim@nasby.net, pgsql-performance@postgresql.org Subject: Re: More tablescanning fun In-reply-to: <1051288086.1765.95.camel@fuji.krosing.net> References: <20030424183817.A66185@flake.decibel.org> <3660.1051228710@sss.pgh.pa.us> <20030424235924.B66185@flake.decibel.org> <1051288086.1765.95.camel@fuji.krosing.net> Comments: In-reply-to Hannu Krosing message dated "25 Apr 2003 19:28:06 +0300" Date: Fri, 25 Apr 2003 16:10:47 -0400 Message-ID: <29560.1051301447@sss.pgh.pa.us> From: Tom Lane X-Spam-Status: No, hits=-32.5 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/212 X-Sequence-Number: 1718 Hannu Krosing writes: > I have been pondering if keeping pages half-empty (or even 70% empty) > could solve both clustering problems and longish updates for much data. You could achieve that pretty easily if you simply don't ever VACUUM FULL ;-) UPDATE has always (AFAIR) attempted to place the new version on the same page as the old, moving it elsewhere only if it doesn't fit. So that part of the logic is already there. > So "VACUUM FULL 65% EMPTY;" could make sense ? Not so much that, as a parameter to CLUSTER telling it to fill pages only x% full. regards, tom lane