]> 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:43:33 +0000 (18:43 -0400)
commit28b11bd1069ed35f45125b4057780cc55b9d716a
tree44d978012eef2e06e4f7ac3b932b6d89d7703ba8
parent40a50a17b905dae233ddb8bb36b7deff9e3abb16
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