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 12BE732A0F0 for ; Sat, 9 Oct 2004 16:07:32 +0100 (BST) 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 83161-02 for ; Sat, 9 Oct 2004 15:07:30 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 0E60B329DBE for ; Sat, 9 Oct 2004 16:07:29 +0100 (BST) 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 i99F7TRX027697; Sat, 9 Oct 2004 11:07:29 -0400 (EDT) To: Kevin Brown Cc: pgsql-performance@postgresql.org Subject: Re: First set of OSDL Shared Mem scalability results, some wierdness ... In-reply-to: <20041009112048.GA665@filer> References: <200410081443.16109.josh@agliodbs.com> <20041009112048.GA665@filer> Comments: In-reply-to Kevin Brown message dated "Sat, 09 Oct 2004 04:20:48 -0700" Date: Sat, 09 Oct 2004 11:07:28 -0400 Message-ID: <27696.1097334448@sss.pgh.pa.us> From: Tom Lane 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: 200410/121 X-Sequence-Number: 8597 Kevin Brown writes: > This is why I sometimes wonder whether or not it would be a win to use > mmap() to access the data and index files -- mmap() is Right Out because it does not afford us sufficient control over when changes to the in-memory data will propagate to disk. The address-space-management problems you describe are also a nasty headache, but that one is the showstopper. regards, tom lane