From b9e3a60bf1369430424f136c6a188c898b0d95f0 Mon Sep 17 00:00:00 2001 From: Peter Smith Date: Wed, 31 Mar 2021 10:19:22 +1100 Subject: [PATCH v2] Use consistent terminology for tablesync slots. 1. Some pages called these tablesync slots. 2. Some pages called these table synchronization slots. For consistency try make them all the same as 2. --- doc/src/sgml/ref/alter_subscription.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/ref/alter_subscription.sgml b/doc/src/sgml/ref/alter_subscription.sgml index 0adf68e..5aed269 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 -- 1.8.3.1