summaryrefslogtreecommitdiff
path: root/src/backend/executor
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-07-28 18:42:59 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2015-07-28 18:42:59 -0400
commit263f225965bd583bf403cbd9d5e1171f1e445bdf (patch)
tree6a3f6a64a12717ccf8de18a2fb3e5d69f0b112c3 /src/backend/executor
parent1a2f95630d4897b81feb299bdf70d10c3c2654c4 (diff)
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')
0 files changed, 0 insertions, 0 deletions