database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-21 12:05:57 +03:00
Code

Fix inaccurate description of tablespace.

Browse Source 
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.
This commit is contained in:
Fujii Masao 2013-07-31 22:36:39 +09:00
parent 9a78f66fdc
commit fe136ba6fc
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/src/sgml/manage-ag.sgml
View File

@ -479,7 +479,8 @@ CREATE TABLE foo(i int);
<para>
To determine the set of existing tablespaces, examine the
<structname>pg_tablespace</> system catalog, for example
<link linkend="catalog-pg-tablespace"><structname>pg_tablespace</structname>
</link> system catalog, for example
<synopsis>
SELECT spcname FROM pg_tablespace;
</synopsis>
@ -498,11 +499,11 @@ SELECT spcname FROM pg_tablespace;
The directory <filename>$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 <structname>pg_tablespace</> catalog with the new
locations. (If you do not, <literal>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 <structname>pg_tablespace</>
catalog with the new locations. (If you do not, <literal>pg_dump</> will
continue to output the old tablespace locations.)
</para>
</sect1>