pgsql: Update our documentation concerning where to create data directo

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Update our documentation concerning where to create data directo
Date: 2015-07-28 22:43:55
Message-ID: E1ZKDbH-0007vs-1j@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/7bdf6d0440697619cea61841cd1432337b151b47

Modified Files
--------------
doc/src/sgml/runtime.sgml | 79 ++++++++++++++++++++++++++++++++-------------
1 file changed, 57 insertions(+), 22 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Joe Conway 2015-07-28 23:03:12 pgsql: Create a pg_shdepend entry for each role in TO clause of policie
Previous Message Andrew Dunstan 2015-07-28 21:59:30 pgsql: Only adjust negative indexes in json_get up to the length of the