Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 9f45631

Browse files
author
Amit Kapila
committed
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
1 parent 0ff8bbd commit 9f45631

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/src/sgml/ref/alter_subscription.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,8 +51,8 @@ ALTER SUBSCRIPTION <replaceable class="parameter">name</replaceable> RENAME TO <
5151

5252
<para>
5353
When refreshing a publication we remove the relations that are no longer
54-
part of the publication and we also remove the tablesync slots if there are
55-
any. It is necessary to remove tablesync slots so that the resources
54+
part of the publication and we also remove the table synchronization slots
55+
if there are any. It is necessary to remove these slots so that the resources
5656
allocated for the subscription on the remote host are released. If due to
5757
network breakdown or some other error, <productname>PostgreSQL</productname>
5858
is unable to remove the slots, an ERROR will be reported. To proceed in this

0 commit comments

Comments
 (0)