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 507505E46F9 for ; Sat, 28 Aug 2004 09:02:15 -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 59493-06 for ; Sat, 28 Aug 2004 12:02:15 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 3E6445E46F3 for ; Sat, 28 Aug 2004 09:02:09 -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 i7SC2ALq062108 for ; Sat, 28 Aug 2004 12:02:10 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i7SBdTR8058055 for pgsql-performance@postgresql.org; Sat, 28 Aug 2004 11:39:29 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Equivalent praxis to CLUSTERED INDEX? Date: Sat, 28 Aug 2004 13:39:31 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 22 Message-ID: <41306EF3.2030304@bigfoot.com> References: <200408280354.i7S3slb21543@candle.pha.pa.us> <87k6vjllve.fsf@stark.xeocode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Greg Stark User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en In-Reply-To: <87k6vjllve.fsf@stark.xeocode.com> 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/412 X-Sequence-Number: 8048 Greg Stark wrote: > Bruce Momjian writes: > > >>>Don't you think this will permit also to avoid extra disk seek and cache >>>invalidation? If you are updating the row (0,1) I think is less expensive >>>put the new version in (0,2) instead of thousand line far from that point. > > > Well if the other buffer "a thousand lines far from that point" is already in > ram, then no, there's no penalty at the time for storing it there. I was wandering about the cache invalidation, may be the ram is big enough but I doubt about the cache, the recommendation in this case is to modify adjacent memory address instead of jumping. Regards Gaetano Mendola