Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 0B5F59F9463 for ; Mon, 1 Oct 2007 20:47:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 42367-05 for ; Mon, 1 Oct 2007 20:47:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 7E92F9F93E5 for ; Mon, 1 Oct 2007 20:47:01 -0300 (ADT) Received: from perhan.alvh.no-ip.org ([190.95.8.15]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l91Nkx9N029096; Mon, 1 Oct 2007 16:47:00 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 0C7F047C6C; Mon, 1 Oct 2007 19:46:52 -0400 (CLT) Date: Mon, 1 Oct 2007 19:46:52 -0400 From: Alvaro Herrera To: Tom Lane Cc: Simon Riggs , Josh Berkus , pgsql-hackers@postgresql.org, Mija Lee Subject: Re: PG on NFS may be just a bad idea Message-ID: <20071001234651.GD9430@alvh.no-ip.org> References: <25517.1191038302@sss.pgh.pa.us> <47012AC5.9040808@agliodbs.com> <1191263814.4260.57.camel@ebony.site> <1191264888.4260.69.camel@ebony.site> <24184.1191281116@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <24184.1191281116@sss.pgh.pa.us> User-Agent: Mutt/1.5.16 (2007-06-11) X-Virus-Scanned: ClamAV 0.91.1/4445/Mon Oct 1 01:32:46 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Mon, 01 Oct 2007 16:47:01 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/45 X-Sequence-Number: 108413 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. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support