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 167615E40AC for ; Thu, 26 Aug 2004 18:31:54 -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 27046-04 for ; Thu, 26 Aug 2004 21:31:51 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 606F65E3F15 for ; Thu, 26 Aug 2004 18:31:50 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i7QLVoLq030474 for ; Thu, 26 Aug 2004 21:31:50 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i7QL9h9o022953 for pgsql-performance@postgresql.org; Thu, 26 Aug 2004 21:09:43 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Equivalent praxis to CLUSTERED INDEX? Date: Thu, 26 Aug 2004 23:09:35 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 18 Message-ID: <412E518F.8090805@bigfoot.com> References: <1093544071.349.106.camel@vulture.corp.neopolitan.com> <200408261818.i7QIIrr09640@candle.pha.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Bruce Momjian User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en In-Reply-To: <200408261818.i7QIIrr09640@candle.pha.pa.us> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-performance@postgresql.org 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/379 X-Sequence-Number: 8015 Bruce Momjian wrote: > How do vendors actually implement auto-clustering? I assume they move > rows around during quiet periods or have lots of empty space in each > value bucket. > > --------------------------------------------------------------------------- IIRC informix doesn't have it, and you have to recluster periodically the table. After having clustered the table with an index in order to recluster the table with another index you have to release the previous one ( ALTER index TO NOT CLUSTER ), the CLUSTER is an index attribute and each table can have only one index with that attribute ON. Regards Gaetano Mendola