From fe136ba6fc31760efe7ac53e662395a71a92dc03 Mon Sep 17 00:00:00 2001 From: Fujii Masao Date: Wed, 31 Jul 2013 22:36:39 +0900 Subject: [PATCH] Fix inaccurate description of tablespace. Currently we don't need to update the pg_tablespace catalog after redefining the symbolic links to the tablespaces because pg_tablespace.spclocation column was removed in PostgreSQL 9.2. Back patch to 9.2 where pg_tablespace.spclocation was removed. Ian Barwick, with minor change by me. --- doc/src/sgml/manage-ag.sgml | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/doc/src/sgml/manage-ag.sgml b/doc/src/sgml/manage-ag.sgml index e5a5947ef2..b44d521ba6 100644 --- a/doc/src/sgml/manage-ag.sgml +++ b/doc/src/sgml/manage-ag.sgml @@ -479,7 +479,8 @@ CREATE TABLE foo(i int); To determine the set of existing tablespaces, examine the - pg_tablespace system catalog, for example + pg_tablespace + system catalog, for example SELECT spcname FROM pg_tablespace; @@ -498,11 +499,11 @@ SELECT spcname FROM pg_tablespace; The directory $PGDATA/pg_tblspc contains symbolic links that point to each of the non-built-in tablespaces defined in the cluster. Although not recommended, it is possible to adjust the tablespace - layout by hand by redefining these links. Two warnings: do not do so - while the server is running; and after you restart the server, - update the pg_tablespace catalog with the new - locations. (If you do not, pg_dump will continue to output - the old tablespace locations.) + layout by hand by redefining these links. Under no circumstances perform + this operation while the server is running. Note that in PostgreSQL 9.1 + and earlier you will also need to update the pg_tablespace + catalog with the new locations. (If you do not, pg_dump will + continue to output the old tablespace locations.)