From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | shikase(at)air(dot)co(dot)jp, pgsql-general(at)postgresql(dot)org |
Subject: | Re: The case of PostgreSQL on NFS Server |
Date: | 2010-06-28 22:36:10 |
Message-ID: | 201006282236.o5SMaAh29960@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Craig Ringer wrote:
> On 24/06/10 12:42, Iwao Shikase wrote:
>
> > In my environment, Database cluster is in NFS server.
>
> So you are mounting an nfs file system shared by "localhost" ?
>
> Why not run PostgreSQL directly on the underlying file system, rather
> than via nfs?
>
> > I guess that, In my environment, the mount options, system synchronously
> > and without cache does not need.
>
> I would still expect to lose some written data if the system crashed or
> lost power and nfs write caching was enabled. Because nfs's caching
> doesn't guarantee write ordering, this data loss would probably horribly
> corrupt your database.
>
> If you can get your NFS implementation to guarantee write ordering then
> it's quite safe to cache. Good luck proving that it's doing the right
> thing, though.
"Safe" meaning it will not corrupt your database, but you could lose
committed transactions after a server crash.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2010-06-29 00:05:04 | Re: XML - DOCTYPE element - documentation suggestion |
Previous Message | raghu ram | 2010-06-28 22:14:19 | Prepared statement issue in Pgpool-II |