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 5302A8BA20C for ; Tue, 15 Feb 2005 17:55:37 +0000 (GMT) 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 89447-03 for ; Tue, 15 Feb 2005 17:55:33 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id F2AC18BA071 for ; Tue, 15 Feb 2005 17:55:30 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j1FHtJKO014043; Tue, 15 Feb 2005 12:55:20 -0500 (EST) To: Josh Berkus Cc: Greg Stark , Mark Aufflick , pgsql-performance@postgresql.org Subject: Re: seq scan cache vs. index cache smackdown In-reply-to: <200502150922.59176.josh@agliodbs.com> References: <9326.1108452962@sss.pgh.pa.us> <87vf8u2qgw.fsf@stark.xeocode.com> <200502150922.59176.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Tue, 15 Feb 2005 09:22:59 -0800" Date: Tue, 15 Feb 2005 12:55:19 -0500 Message-ID: <14042.1108490119@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/240 X-Sequence-Number: 10569 Josh Berkus writes: > Why is mmap not workable? We can't control write order. There are other equally bad problems, but that one alone eliminates it from consideration. See past discussions. regards, tom lane