From: Alvaro Herrera <alvherre@commandprompt.com>
To: 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, 1 Oct 2007 19:46:52 -0400
Message-ID: <20071001234651.GD9430@alvh.no-ip.org> (raw)
In-Reply-To: <24184.1191281116@sss.pgh.pa.us>
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>
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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: 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: <20071001234651.GD9430@alvh.no-ip.org>
* 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