From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Joe Conway <mail@joeconway.com>
To: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Update section on NFS
Date: Tue, 23 Apr 2019 17:11:26 +0200
Message-ID: <bfb2bb68-c4f1-bf11-b4b8-07f68027e4e9@2ndquadrant.com> (raw)
In-Reply-To: <950271f0-d8f3-a367-14b7-1f91e4d15e40@joeconway.com>
References: <e90f24bb-5423-6abb-58ec-501176eb4afc@2ndquadrant.com>
<83a5bea3-57cd-e820-83eb-4a9c64082c19@joeconway.com>
<9c9c8a4c-5d69-cdbd-60c8-442ff7906d5b@2ndquadrant.com>
<950271f0-d8f3-a367-14b7-1f91e4d15e40@joeconway.com>
On 2019-04-23 16:15, Joe Conway wrote:
> On 4/23/19 9:47 AM, Peter Eisentraut wrote:
>> On 2019-04-23 14:31, Joe Conway wrote:
>>> Looks like you dropped the advice WRT the asynchronous mount option.
>>> Isn't that is still relevant?
>>
>> I don't think that advice was correct. An async mounted NFS file system
>> will flush data on fsync, which is what one wants.
>>
>
> I don't think so. Not sure if you have an account at Red Hat, but this
> ticket covers it:
>
> https://access.redhat.com/solutions/48199
That discusses the equally-named export options on the NFS server, not
the mount options on the NFS client.
You generally do want the sync option on the server so that an fsync
from the client actually reaches the *disk*, not just the memory, of the
NFS server.
But you don't need the sync option on the client.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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: peter.eisentraut@2ndquadrant.com, mail@joeconway.com
Subject: Re: Update section on NFS
In-Reply-To: <bfb2bb68-c4f1-bf11-b4b8-07f68027e4e9@2ndquadrant.com>
* 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