| From: | George Barnett <gbarnett(at)atlassian(dot)com> |
|---|---|
| To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch to improve reliability of postgresql on linux nfs |
| Date: | 2011-09-12 04:30:17 |
| Message-ID: | B36F0954-8831-47FA-8333-0EF4DF234F1A@atlassian.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/09/2011, at 1:30 AM, Bernd Helmle wrote:
> --On 9. September 2011 10:27:22 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> On the whole I think you'd be better off lobbying your NFS implementors
>> to provide something closer to the behavior of every other filesystem on
>> the planet. Or checking to see if you need to adjust your NFS
>> configuration, as the other responders mentioned.
>
> You really need at least mount options 'hard' _and_ 'nointr' on NFS mounts, otherwise you are out of luck. Oracle and DB2 guys recommend those settings and without them any millisecond of network glitch could disturb things unreasonably.
Hi,
My mount options include hard and intr.
George
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2011-09-12 05:59:32 | Re: Patch to improve reliability of postgresql on linux nfs |
| Previous Message | David E. Wheeler | 2011-09-12 04:21:28 | What Would You Like To Do? |