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:42:59 -0400 |
commit | 7bdf6d0440697619cea61841cd1432337b151b47 (patch) | |
tree | 3cb3c95a04f249eb779a20d9159b3a873361f082 /src/backend/executor/nodeHash.c | |
parent | 47ee27521ac0a59e14b1f0f86d8cef1c7fa0ddff (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/nodeHash.c')
0 files changed, 0 insertions, 0 deletions