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 9D6615E46E1 for ; Fri, 27 Aug 2004 15:32:18 -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 10924-01 for ; Fri, 27 Aug 2004 18:32:08 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 8547D5E46C1 for ; Fri, 27 Aug 2004 15:32:04 -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 i7RIW3Lq010909 for ; Fri, 27 Aug 2004 18:32:03 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i7RIQh9v008840 for pgsql-performance@postgresql.org; Fri, 27 Aug 2004 18:26:43 GMT From: Mischa Sandberg Reply-To: ischamay.andbergsay@activestateway.com User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Equivalent praxis to CLUSTERED INDEX? References: <118B3D82-F850-11D8-8B8C-000A95C4BD7A@sf.net> <200408271748.i7RHmfJ15766@candle.pha.pa.us> In-Reply-To: <200408271748.i7RHmfJ15766@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Lines: 23 Message-ID: Date: Fri, 27 Aug 2004 18:26:39 GMT To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.1 tagged_above=0.0 required=5.0 tests=NO_DNS_FOR_FROM X-Spam-Level: * X-Archive-Number: 200408/418 X-Sequence-Number: 8054 I think you've probably fingered the kicker of why PG doesn't have this kind of clustering already. Hence perhaps the need for other approaches to the issue (the disk-IO efficiency of reading groups of rows related by a common key) that other DB's (with in-place update) address with synchronous clustering ('heap rebalancing' ?). Bruce Momjian wrote: > Adi Alurkar wrote: > >>IIRC it it to reduce the "overflow" of data or what oracle calls >>chained rows. i.e if a table has variable length columns and 10 rows >>get inserted into a datapage, if this datapage is full and one of the >>variable length field gets updated the row will now "overflow" into >>another datapage, but if the datapage is created with an appropriate >>amount of free space the updated row will be stored in one single >>datapage. > > > Agreed. What I am wondering is with our system where every update gets > a new row, how would this help us? I know we try to keep an update on > the same row as the original, but is there any significant performance > benefit to doing that which would offset the compaction advantage? >