From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: IO scheduler recommendation
Date: Tue, 22 Jan 2019 10:21:30 +0100
Message-ID: <90f7dc4ae8f31543093cb6d618135ceb7dee5fac.camel@cybertec.at> (raw)
In-Reply-To: <612605b8-c94b-68a3-3e8f-0134ddcfe71d@gmail.com>
References: <CAHMim6rF6jxUp1ueJP593SwM4so7jsZC0vZaXOX2yD_z4XF9xQ@mail.gmail.com>
<df772cb764b99d4f4a454ee307840022c91bcdb6.camel@cybertec.at>
<CAHMim6qzmodYXJtnOQBU-ge5Q0WHKsPOkFkLMSBLB5YShae0oQ@mail.gmail.com>
<CAC=50j-j3e7NX2mPGLYfsoPTVVq=Nrp4TPesLKDrNxQK+snUDg@mail.gmail.com>
<612605b8-c94b-68a3-3e8f-0134ddcfe71d@gmail.com>
Ron wrote:
> Isn't the use of NFS pretty high on the "things not to do with Postgres" list?
There is a strong sentiment against PostgreSQL on NFS, voiced by people
I tend to trust, but the only detailed horror story I have heard is about
a "bg" mounted NFS file system that wasn't mounted yet when PostgreSQL
was started, and the startup script decided to run "initdb", during which
the mount finally succeeded.
If you browse the archives you will read that "NFS is unreliable" and
"it depends on the implementation, but Linux' implementation is bad"
and such, but without any technical detail ever being mentioned.
That may not be the fault of the people who propagate these opinions -
perhaps they experienced database corruption using NFS, but don't know
exactly which part of NFS caused the problem exactly how.
There are some other voices that say that it works just fine, if you
configure it properly.
The feeling I get from all this is that it is an experimental field,
and everybody who wants to use it would be well advised to run tests
covering all kinds of crash scenarios under load.
I'd still be curious to know if there is someone who can supply
technical details about what *exactly* is wrong with NFS.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
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-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: IO scheduler recommendation
In-Reply-To: <90f7dc4ae8f31543093cb6d618135ceb7dee5fac.camel@cybertec.at>
* 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