Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit480d4f7

Browse files
committed
Document that soft-mounting NFS is not recommended.
1 parentfca9fff commit480d4f7

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

‎doc/src/sgml/runtime.sgml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.409 2008/02/26 18:01:26 petere Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.410 2008/03/21 14:23:37 momjian Exp $ -->
22

33
<chapter Id="runtime">
44
<title>Operating System Environment</title>
@@ -183,7 +183,8 @@ postgres$ <userinput>initdb -D /usr/local/pgsql/data</userinput>
183183
Specifically, delayed (asynchronous) writes to the <acronym>NFS</>
184184
server can cause reliability problems; if possible, mount
185185
<acronym>NFS</> file systems synchronously (without caching) to avoid
186-
this. (Storage Area Networks (<acronym>SAN</>) use a low-level
186+
this. Also, soft-mounting <acronym>NFS</> is not recommended.
187+
(Storage Area Networks (<acronym>SAN</>) use a low-level
187188
communication protocol rather than <acronym>NFS</>.)
188189
</para>
189190

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp