From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Update section on NFS |
Date: | 2019-04-24 11:17:08 |
Message-ID: | b49cf673-c14b-094c-3059-39d3279fb635@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 4/24/19 4:54 AM, Peter Eisentraut wrote:
> On 2019-04-23 18:53, Tom Lane wrote:
>> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>>> On 2019-04-23 16:15, Joe Conway wrote:
>>>> 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.
>>
>> Well, the DBA might also be the NFS server's admin, so I think we ought
>> to explain the correct settings on both ends.
>
> Right, the slight confusion in this thread indicates that this is worth
> explaining further.
And the confusion is aided by the fact that prior to NFS 3 sync *was*
necessary on the client side. Yeah I know, ancient, so maybe only old
folks like me get confused ;-), but NFS 2 was probably current when this
was originally written.
See: http://nfs.sourceforge.net/
"safe asynchronous writes."
> New version attached.
Looks reasonable to me.
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2019-04-24 11:22:03 | Re: Passphrase protected SSL key and reloads |
Previous Message | Peter Eisentraut | 2019-04-24 08:54:44 | Re: Update section on NFS |