Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 8F8489FA150 for ; Mon, 8 Oct 2007 17:46:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 24791-04-3 for ; Mon, 8 Oct 2007 17:46:42 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 1A2669FA0BC for ; Mon, 8 Oct 2007 17:46:45 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l98KkQj28574; Mon, 8 Oct 2007 16:46:26 -0400 (EDT) From: Bruce Momjian Message-Id: <200710082046.l98KkQj28574@momjian.us> Subject: Re: PG on NFS may be just a bad idea In-Reply-To: <20071001234651.GD9430@alvh.no-ip.org> To: Alvaro Herrera Date: Mon, 8 Oct 2007 16:46:26 -0400 (EDT) CC: Tom Lane , Simon Riggs , Josh Berkus , pgsql-hackers@postgresql.org, Mija Lee X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/258 X-Sequence-Number: 108626 Alvaro Herrera wrote: > Tom Lane wrote: > > Simon Riggs writes: > > > http://blogs.netapp.com/dave/2007/08/oracle-optimize.html > > > > Not a whole lot of technical content there, but pretty interesting > > nonetheless. I *think* that the issues we're seeing are largely in the > > NFS client-side kernel code, so bypassing that stack as Oracle is doing > > might eliminate the problem. Of course, there's a sizable amount of > > code to be written to do that ... > > Yeah. Next step we will be writing our own malloc. I assume there should be a ;-) in there because we already have our own malloc (palloc). -- Bruce Momjian http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +