it seems more logical there.
-
+
Managing Databases
the old tablespace locations.)
-
-
Network File Systems
-
-
-
-
NFS>>Network File Systems>>
-
Network Attached Storage (NAS>)>Network File Systems>>
-
- Many installations create tablespace on network file systems.
- Sometimes this is done directly via
NFS>, or by using a
- Network Attached Storage (
NAS>) device that uses
-
NFS> internally. PostgreSQL> does nothing
- special for
NFS> file systems, meaning it assumes
-
NFS> behaves exactly like locally-connected drives. If
- client and server
NFS> implementations have non-standard
- semantics, this can cause reliability problems (see
- url="http://www.time-travellers.org/shane/papers/NFS_considered_harmful.html">).
- Specifically, delayed (asynchonous) writes to the
NFS>
- server can cause reliability problems; if possible, mount
-
NFS> file systems synchonously to avoid this.
-
-
-
-
-
+
Operating System Environment
locale setting. For details see .
- If using non-local (network) file systems, see
- linkend="manage-ag-tablespaces-nfs">.
-
+
+
Network File Systems
+
+
+
+
NFS>>Network File Systems>>
+
Network Attached Storage (NAS>)>Network File Systems>>
+
+ Many installations create database clusters on network file systems.
+ Sometimes this is done directly via
NFS>, or by using a
+ Network Attached Storage (
NAS>) device that uses
+
NFS> internally. PostgreSQL> does nothing
+ special for
NFS> file systems, meaning it assumes
+
NFS> behaves exactly like locally-connected drives
+ (
DAS>, Direct Attached Storage). If client and server
+
NFS> implementations have non-standard semantics, this can
+ cause reliability problems (see
+ url="http://www.time-travellers.org/shane/papers/NFS_considered_harmful.html">).
+ Specifically, delayed (asynchonous) writes to the
NFS>
+ server can cause reliability problems; if possible, mount
+
NFS> file systems synchonously (without caching) to avoid
+ this. (Storage Area Networks (
SAN>) use a low-level
+ communication protocol rather than
NFS>.)
+
+
+