X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 0217CD1B4C6 for ; Mon, 5 Jan 2004 18:55:10 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 36809-10 for ; Mon, 5 Jan 2004 14:54:20 -0400 (AST) Received: from cayenne.palmdigitalmedia.com (cayenne.palmdigitalmedia.com [63.110.43.230]) by svr1.postgresql.org (Postfix) with SMTP id 7742FD1B43A for ; Mon, 5 Jan 2004 14:54:05 -0400 (AST) Received: (qmail 6219 invoked from network); 5 Jan 2004 18:54:06 -0000 Received: from unknown (HELO ?192.168.124.23?) (63.110.43.226) by 0 with SMTP; 5 Jan 2004 18:54:06 -0000 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Mon, 05 Jan 2004 13:54:16 -0500 Subject: Re: Incremental clustering? From: John Siracusa To: Postgres Admin Message-ID: In-Reply-To: Mime-version: 1.0 Reply-To: siracusa@mindspring.com Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/50 X-Sequence-Number: 11913 On 1/4/04 6:24 PM, Christopher Browne wrote: > The cluster operation potentially has to reorder all the tuples, and > the fact that the table is already _partially_ organized only > diminishes the potential. If the new data, generally added "at the > end," has values that are fairly uniformly distributed across the > index, then the operation really will have to reorder all of the > tuples... What about the special case of a table that is clustered on a column and all subsequent inserts will add rows with ever-increasing values of that column? This would be the case for creation dates or even a column created from a sequence. Basically, after clustering, it would be nice if you could tell the system to "only add to the end" and to "add in clustered order." Programming for special cases is annoying, but sometimes it really helps. -John