diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2015-07-28 18:42:59 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2015-07-28 18:43:30 -0400 |
commit | 8c72a7fab47a7f501d211468d6e477e1f3a20599 (patch) | |
tree | 6e03473f5781bf889f22553ec421c6965ae19b59 /src/backend/executor/nodeRecursiveunion.c | |
parent | 6d10f4e9d7f0051afb60c42409f2fe61cf4da348 (diff) | |
download | postgresql-8c72a7fab47a7f501d211468d6e477e1f3a20599.tar.gz postgresql-8c72a7fab47a7f501d211468d6e477e1f3a20599.zip |
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.
Diffstat (limited to 'src/backend/executor/nodeRecursiveunion.c')
0 files changed, 0 insertions, 0 deletions