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:33 -0400 |
commit | 28b11bd1069ed35f45125b4057780cc55b9d716a (patch) | |
tree | 44d978012eef2e06e4f7ac3b932b6d89d7703ba8 /src/backend/parser/parse_expr.c | |
parent | 40a50a17b905dae233ddb8bb36b7deff9e3abb16 (diff) | |
download | postgresql-28b11bd1069ed35f45125b4057780cc55b9d716a.tar.gz postgresql-28b11bd1069ed35f45125b4057780cc55b9d716a.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/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions