postgres.git / summary / log / commit / refs

commit    308724bcc3b9c1aeb33ce04e232e5199518fa06a
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Wed Feb 05 18:06:11 2020 +0000
First released in: 13.0, 10.12, 11.7, 12.2

    ALTER SUBSCRIPTION / REFRESH docs: explain copy_data
    
    The docs are ambiguous as to which tables would be copied over when the
    copy_data parameter is true in ALTER SUBSCRIPTION ... REFRESH PUBLICATION.
    Make it clear that it only applies to tables which are new in the
    publication.
    
    Author: David Christensen (reword by Álvaro Herrera)
    Discussion: https://postgr.es/m/95339420-7F09-4F8C-ACC0-8F1CFAAD9CD7@endpoint.com


 doc/src/sgml/ref/alter_subscription.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/alter_subscription.sgml b/doc/src/sgml/ref/alter_subscription.sgml
index 6dfb2e4d3e0..1b8beadbaa5 100644
--- a/doc/src/sgml/ref/alter_subscription.sgml
+++ b/doc/src/sgml/ref/alter_subscription.sgml
@@ -128,7 +128,8 @@ ALTER SUBSCRIPTION <replaceable class="parameter">name</replaceable> RENAME TO <
          <para>
           Specifies whether the existing data in the publications that are
           being subscribed to should be copied once the replication starts.
-          The default is <literal>true</literal>.
+          The default is <literal>true</literal>.  (Previously subscribed
+          tables are not copied.)
          </para>
         </listitem>
        </varlistentry>


[parent: 78a26c3edd85]