From: Bruce Momjian <bruce@momjian.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-hackers@postgresql.org, Mija Lee <mija@scharp.org>
Subject: Re: PG on NFS may be just a bad idea
Date: Mon, 8 Oct 2007 16:46:26 -0400 (EDT)
Message-ID: <200710082046.l98KkQj28574@momjian.us> (raw)
In-Reply-To: <20071001234651.GD9430@alvh.no-ip.org>
Alvaro Herrera wrote:
> Tom Lane wrote:
> > Simon Riggs <simon@2ndquadrant.com> 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 <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, alvherre@commandprompt.com, tgl@sss.pgh.pa.us, simon@2ndquadrant.com, josh@agliodbs.com, mija@scharp.org
Subject: Re: PG on NFS may be just a bad idea
In-Reply-To: <200710082046.l98KkQj28574@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox