diff options
author | Amit Kapila <akapila@postgresql.org> | 2022-06-24 08:37:26 +0530 |
---|---|---|
committer | Amit Kapila <akapila@postgresql.org> | 2022-06-24 08:37:26 +0530 |
commit | 1ce34519c79e9eed1b6b8dd2f47ae95564e739d7 (patch) | |
tree | f7123e2cb3cdbfd501a5f42e091a08374bfac459 /doc/src/sgml/ref/create_subscription.sgml | |
parent | 75f2171e6c8fa4e1f0ce4fdbf907ee7d0fcb404d (diff) |
Doc: clarify that tablesync ignores publish operation.
This patch documents that the initial data synchronization (tablesync) for
logical replication does not take into account the publication 'publish'
parameter when copying the existing table data.
Author: Peter Smith
Reviewed-by: Shi yu, Euler Taveira, Robert Haas, Amit Kapila
Discussion: https://postgr.es/m/CAHut+PtbfALjFpS2MkrvQ+wWQKByP7CNh9RtFta-r=BHEU3S3w@mail.gmail.com
Diffstat (limited to 'doc/src/sgml/ref/create_subscription.sgml')
-rw-r--r-- | doc/src/sgml/ref/create_subscription.sgml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/src/sgml/ref/create_subscription.sgml b/doc/src/sgml/ref/create_subscription.sgml index 35b39c28dac..34b3264b261 100644 --- a/doc/src/sgml/ref/create_subscription.sgml +++ b/doc/src/sgml/ref/create_subscription.sgml @@ -353,6 +353,10 @@ CREATE SUBSCRIPTION <replaceable class="parameter">subscription_name</replaceabl 15 then any row filtering is ignored during the initial data synchronization phase. For this case, the user might want to consider deleting any initially copied data that would be incompatible with subsequent filtering. + Because initial data synchronization does not take into account the publication + <literal>publish</literal> parameter when copying existing table data, some rows + may be copied that would not be replicated using DML. See + <xref linkend="logical-replication-subscription-examples"/> for examples. </para> <para> |