| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: NFS, file system cache and shared_buffers |
| Date: | 2014-05-29 00:36:04 |
| Message-ID: | 538680F4.1070501@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>> Why would they implement their own client? Did they have to do something special in their client to
>> make it safe?
>
> I think it is mostly a performance issue. Each backend mounts its own copy
> of the data files it needs.
I personally would never put PostgreSQL on an NFS share on Linux.
Unless things have changed radically in the last couple years, Linux's
NFS code is flaky and unreliable, including flat-out lying about whether
stuff has been sent and received or not. This is why NetApp's NFS
servers came with their own, proprietary, Linux kernel module.
NFS on Solaris/Illumos is a different story. Not sure about FreeBSD.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2014-05-30 07:12:05 | Re: NFS, file system cache and shared_buffers |
| Previous Message | Grzegorz Olszewski | 2014-05-28 21:03:22 | Re: Planner doesn't take indexes into account |