Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit9f45631

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 otherplaces as table synchronization slots. For consistency, we refer to them astable synchronization slots at all places.Author: Peter SmithReviewed-by: Amit KapilaDiscussion:https://postgr.es/m/CAHut+PvzYNKCeZ=kKBDkh3dw-r=2D3fk=nNc9SXSW=CZGk69xg@mail.gmail.com
1 parent0ff8bbd commit9f45631

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 thetablesync slots if there are
55-
any. It is necessary to removetablesync slots so that the resources
54+
part of the publication and we also remove thetable synchronization slots
55+
if there areany. It is necessary to removethese 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)

[8]ページ先頭

©2009-2025 Movatter.jp