X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id BC14FD1C4B9 for ; Mon, 28 Jul 2003 16:58:21 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 03074-05 for ; Mon, 28 Jul 2003 13:57:26 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id C447FD1C4EE for ; Mon, 28 Jul 2003 13:58:20 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h6SGwJQ3015251; Mon, 28 Jul 2003 12:58:19 -0400 (EDT) To: Josh Berkus Cc: pgsql-performance@postgresql.org Subject: Re: Mapping a database completly into Memory In-reply-to: <200307280950.36076.josh@agliodbs.com> References: <97842368.20030727104901@artis.uni-oldenburg.de> <1059401815.749.7.camel@taz.oficina> <10185.1059409557@sss.pgh.pa.us> <200307280950.36076.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Mon, 28 Jul 2003 09:50:36 -0700" Date: Mon, 28 Jul 2003 12:58:19 -0400 Message-ID: <15250.1059411499@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/449 X-Sequence-Number: 2742 Josh Berkus writes: >> If we had a portable way >> of preventing the kernel from caching the same page, it would make more >> sense to run with large shared_buffers. > Really? I thought we wanted to move the other way ... that is, if we could > get over the portability issues, eliminate shared_buffers entirely and rely > completely on the OS cache. That seems unlikely to happen: there are cache-coherency problems if you don't do your page-level access through shared buffers. Some have suggested using mmap access to the data files in place of shared memory, but that introduces a slew of issues of its own. It might happen but I'm not holding my breath. regards, tom lane