Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit e1a76db

Browse files
committed
doc: improve tablespace example query and link to helper funcs.
Reported-by: Agustín Discussion: https://postgr.es/m/172609721070.1128084.6724666076293146476@wrigleys.postgresql.org Backpatch-through: master
1 parent 4200fea commit e1a76db

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

doc/src/sgml/manage-ag.sgml

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -530,9 +530,11 @@ CREATE TABLE foo(i int);
530530
<link linkend="catalog-pg-tablespace"><structname>pg_tablespace</structname>
531531
</link> system catalog, for example
532532
<synopsis>
533-
SELECT spcname FROM pg_tablespace;
533+
SELECT spcname, spcowner::regrole, pg_tablespace_location(oid) FROM pg_tablespace;
534534
</synopsis>
535-
The <xref linkend="app-psql"/> program's <literal>\db</literal> meta-command
535+
It is possible to find which databases use which tablespaces;
536+
see <xref linkend="functions-info-catalog-table"/>. The <xref
537+
linkend="app-psql"/> program's <literal>\db</literal> meta-command
536538
is also useful for listing the existing tablespaces.
537539
</para>
538540

@@ -541,10 +543,7 @@ SELECT spcname FROM pg_tablespace;
541543
point to each of the non-built-in tablespaces defined in the cluster.
542544
Although not recommended, it is possible to adjust the tablespace
543545
layout by hand by redefining these links. Under no circumstances perform
544-
this operation while the server is running. Note that in PostgreSQL 9.1
545-
and earlier you will also need to update the <structname>pg_tablespace</structname>
546-
catalog with the new locations. (If you do not, <literal>pg_dump</literal> will
547-
continue to output the old tablespace locations.)
546+
this operation while the server is running.
548547
</para>
549548

550549
</sect1>

0 commit comments

Comments
 (0)