]> granicus.if.org Git - postgresql/commit
Update our documentation concerning where to create data directories.
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 28 Jul 2015 22:42:59 +0000 (18:42 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 28 Jul 2015 22:42:59 +0000 (18:42 -0400)
commitadf0072ab8ae283ab26793f0cd8acb5685910b3c
treebd81d75a9581cd0f19c594a5531e6b57cf4633c0
parent3f12041e7ca85ef57e48f0a12f6ae3e32c2e442f
Update our documentation concerning where to create data directories.

Although initdb has long discouraged use of a filesystem mount-point
directory as a PG data directory, this point was covered nowhere in the
user-facing documentation.  Also, with the popularity of pg_upgrade,
we really need to recommend that the PG user own not only the data
directory but its parent directory too.  (Without a writable parent
directory, operations such as "mv data data.old" fail immediately.
pg_upgrade itself doesn't do that, but wrapper scripts for it often do.)

Hence, adjust the "Creating a Database Cluster" section to address
these points.  I also took the liberty of wordsmithing the discussion
of NFS a bit.

These considerations aren't by any means new, so back-patch to all
supported branches.
doc/src/sgml/runtime.sgml