diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/ref/pg_dump.sgml | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 53b5dd52394..6cf7e570efa 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -799,19 +799,6 @@ PostgreSQL documentation </varlistentry> <varlistentry> - <term><option>--no-subscription-connect</option></term> - <listitem> - <para> - When dumping logical replication subscriptions, - generate <command>CREATE SUBSCRIPTION</command> commands that do not - make remote connections for creating replication slot or initial table - copy. That way, the dump can be restored without requiring network - access to the remote servers. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><option>--no-synchronized-snapshots</></term> <listitem> <para> @@ -1235,6 +1222,19 @@ CREATE DATABASE foo WITH TEMPLATE template0; in cross-version cases, as it can prevent problems arising from varying reserved-word lists in different <productname>PostgreSQL</> versions. </para> + + <para> + When dumping logical replication subscriptions, + <application>pg_dump</application> will generate <command>CREATE + SUBSCRIPTION</command> commands that use the <literal>NOCONNECT</literal> + option, so that restoring the subscription does not make remote connections + for creating a replication slot or for initial table copy. That way, the + dump can be restored without requiring network access to the remote + servers. It is then up to the user to reactivate the subscriptions in a + suitable way. If the involved hosts have changed, the connection + information might have to be changed. It might also be appropriate to + truncate the target tables before initiating a new full table copy. + </para> </refsect1> <refsect1 id="pg-dump-examples"> |