aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/ref/pg_basebackup.sgml16
-rw-r--r--doc/src/sgml/ref/pg_receivewal.sgml13
2 files changed, 18 insertions, 11 deletions
diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml
index 4f99340c1dd..c2d721208b1 100644
--- a/doc/src/sgml/ref/pg_basebackup.sgml
+++ b/doc/src/sgml/ref/pg_basebackup.sgml
@@ -807,14 +807,18 @@ PostgreSQL documentation
will override any conflicting command line options.
</para>
<para>
- The option is called <literal>--dbname</literal> for consistency with other
+ This option is called <literal>--dbname</literal> for consistency with other
client applications, but because <application>pg_basebackup</application>
doesn't connect to any particular database in the cluster, any database
- name in the connection string will be ignored
- by <productname>PostgreSQL</productname>. Middleware, or proxies, used in
- connecting to <productname>PostgreSQL</productname> might however
- utilize the value. The database name specified in connection string can
- also be used by <link linkend="logicaldecoding-replication-slots-synchronization">
+ name included in the connection string will be ignored by the server.
+ However, a database name supplied that way overrides the default
+ database name (<literal>replication</literal>) for purposes of
+ looking up the replication connection's password
+ in <filename>~/.pgpass</filename>. Similarly, middleware or proxies
+ used in connecting to <productname>PostgreSQL</productname> might
+ utilize the name for purposes such as connection routing. The
+ database name can also be used
+ by <link linkend="logicaldecoding-replication-slots-synchronization">
logical replication slot synchronization</link>.
</para>
</listitem>
diff --git a/doc/src/sgml/ref/pg_receivewal.sgml b/doc/src/sgml/ref/pg_receivewal.sgml
index 8944eee2a36..9e353a068e5 100644
--- a/doc/src/sgml/ref/pg_receivewal.sgml
+++ b/doc/src/sgml/ref/pg_receivewal.sgml
@@ -315,13 +315,16 @@ PostgreSQL documentation
will override any conflicting command line options.
</para>
<para>
- The option is called <literal>--dbname</literal> for consistency with other
+ This option is called <literal>--dbname</literal> for consistency with other
client applications, but because <application>pg_receivewal</application>
doesn't connect to any particular database in the cluster, any database
- name in the connection string will be ignored by
- <productname>PostgreSQL</productname>. Middleware, or proxies, used in
- connecting to <productname>PostgreSQL</productname> might however
- utilize the value.
+ name included in the connection string will be ignored by the server.
+ However, a database name supplied that way overrides the default
+ database name (<literal>replication</literal>) for purposes of
+ looking up the replication connection's password
+ in <filename>~/.pgpass</filename>. Similarly, middleware or proxies
+ used in connecting to <productname>PostgreSQL</productname> might
+ utilize the name for purposes such as connection routing.
</para>
</listitem>
</varlistentry>