X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 663825E3639 for ; Fri, 27 Aug 2004 01:35:12 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 40367-06 for ; Fri, 27 Aug 2004 04:35:16 +0000 (GMT) Received: from candle.pha.pa.us (candle.pha.pa.us [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 6EE405E46C3 for ; Fri, 27 Aug 2004 01:35:06 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id i7R4Z7N25250; Fri, 27 Aug 2004 00:35:07 -0400 (EDT) From: Bruce Momjian Message-Id: <200408270435.i7R4Z7N25250@candle.pha.pa.us> Subject: Re: Equivalent praxis to CLUSTERED INDEX? In-Reply-To: <87pt5dnta9.fsf@stark.xeocode.com> To: Greg Stark Date: Fri, 27 Aug 2004 00:35:07 -0400 (EDT) Cc: "J. Andrew Rogers" , Magnus Hagander , pgsql-performance@postgresql.org, mischa.sandberg@telus.net X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/383 X-Sequence-Number: 8019 OK, new wording: o Automatically maintain clustering on a table This might require some background daemon to maintain clustering during periods of low usage. It might also require tables to be only paritally filled for easier reorganization. Another idea would be to create a merged heap/index data file so an index lookup would automatically access the heap data too. --------------------------------------------------------------------------- Greg Stark wrote: > > Bruce Momjian writes: > > > Updated TODO item: > > > > o Automatically maintain clustering on a table > > > > This would require some background daemon to maintain clustering > > during periods of low usage. It might also require tables to be only > > paritally filled for easier reorganization. It also might require > > creating a merged heap/index data file so an index lookup would > > automatically access the heap data too. > > Fwiw, I would say the first "would" is also a "might". None of the previous > discussions here presumed a maintenance daemon. The discussions before talked > about a mechanism to try to place new tuples as close as possible to the > proper index position. > > I would also suggest making some distinction between a cluster system similar > to what we have now but improved to maintain the clustering continuously, and > an actual index-organized-table where the tuples are actually only stored in a > btree structure. > > They're two different approaches to similar problems. But they might both be > useful to have, and have markedly different implementation details. > > -- > greg > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073