From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, Mija Lee <mija(at)scharp(dot)org> |
Subject: | Re: PG on NFS may be just a bad idea |
Date: | 2007-10-01 23:46:52 |
Message-ID: | 20071001234651.GD9430@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers pgsql-novice |
Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2007-10-03 22:27:50 | Use of "postmaster" |
Previous Message | Tom Lane | 2007-10-01 23:25:16 | Re: PG on NFS may be just a bad idea |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-10-01 23:48:27 | Re: First steps with 8.3 and autovacuum launcher |
Previous Message | Alvaro Herrera | 2007-10-01 23:43:45 | Re: First steps with 8.3 and autovacuum launcher |
From | Date | Subject | |
---|---|---|---|
Next Message | sandy_mcd@juno.com | 2007-10-02 03:31:29 | how to edit entries in vendor supplied database? |
Previous Message | Tom Lane | 2007-10-01 23:25:16 | Re: PG on NFS may be just a bad idea |