agora inbox for [email protected]
help / color / mirror / Atom feedFrom: Kyotaro Horiguchi <[email protected]>
Subject: [PATCH 5/5] Documentation update
Date: Wed, 24 Apr 2019 16:02:47 +0900
---
doc/src/sgml/ref/create_tablespace.sgml | 5 +++--
doc/src/sgml/ref/pg_basebackup.sgml | 4 ++--
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/doc/src/sgml/ref/create_tablespace.sgml b/doc/src/sgml/ref/create_tablespace.sgml
index c621ec2c6b..e2e9625483 100644
--- a/doc/src/sgml/ref/create_tablespace.sgml
+++ b/doc/src/sgml/ref/create_tablespace.sgml
@@ -94,8 +94,9 @@ CREATE TABLESPACE <replaceable class="parameter">tablespace_name</replaceable>
The directory that will be used for the tablespace. The directory
must exist (<command>CREATE TABLESPACE</command> will not create it),
should be empty, and must be owned by the
- <productname>PostgreSQL</productname> system user. The directory must be
- specified by an absolute path name.
+ <productname>PostgreSQL</productname> system user. The directory may
+ be specified by a relative path name based on the data directory but
+ must not be inside the data directory.
</para>
</listitem>
</varlistentry>
diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml
index fc9e222f8d..ba9ba13b4c 100644
--- a/doc/src/sgml/ref/pg_basebackup.sgml
+++ b/doc/src/sgml/ref/pg_basebackup.sgml
@@ -238,8 +238,8 @@ PostgreSQL documentation
path specification of the tablespace as it is currently defined. (But
it is not an error if there is no tablespace
in <replaceable>olddir</replaceable> contained in the backup.)
- Both <replaceable>olddir</replaceable>
- and <replaceable>newdir</replaceable> must be absolute paths. If a
+ If <replaceable>newdir</replaceable> is a relative path,
+ it is translated based on the output directory. If a
path happens to contain a <literal>=</literal> sign, escape it with a
backslash. This option can be specified multiple times for multiple
tablespaces. See examples below.
--
2.16.3
----Next_Part(Wed_Apr_24_17_02_28_2019_644)----
view thread (2+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: [PATCH 5/5] Documentation update
In-Reply-To: <no-message-id-1883288@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox