From: Amit Kapila Date: Wed, 31 Mar 2021 02:47:50 +0000 (+0530) Subject: Doc: Use consistent terminology for tablesync slots. X-Git-Tag: REL_14_BETA1~413 X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=9f45631766bd0c51a74102770737ba3b0561977e;p=postgresql.git Doc: Use consistent terminology for tablesync slots. At some places in the docs, we refer to them as tablesync slots and at other places as table synchronization slots. For consistency, we refer to them as table synchronization slots at all places. Author: Peter Smith Reviewed-by: Amit Kapila Discussion: https://postgr.es/m/CAHut+PvzYNKCeZ=kKBDkh3dw-r=2D3fk=nNc9SXSW=CZGk69xg@mail.gmail.com --- diff --git a/doc/src/sgml/ref/alter_subscription.sgml b/doc/src/sgml/ref/alter_subscription.sgml index 0adf68eccaf..5aed2694350 100644 --- a/doc/src/sgml/ref/alter_subscription.sgml +++ b/doc/src/sgml/ref/alter_subscription.sgml @@ -51,8 +51,8 @@ ALTER SUBSCRIPTION name RENAME TO < When refreshing a publication we remove the relations that are no longer - part of the publication and we also remove the tablesync slots if there are - any. It is necessary to remove tablesync slots so that the resources + part of the publication and we also remove the table synchronization slots + if there are any. It is necessary to remove these slots so that the resources allocated for the subscription on the remote host are released. If due to network breakdown or some other error, PostgreSQL is unable to remove the slots, an ERROR will be reported. To proceed in this