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

Commit2f8d636

Browse files
committed
doc: mention wal_receiver_status_interval as GUC affecting logical rep worker.
wal_receiver_timeout, wal_receiver_status_interval andwal_retrieve_retry_interval configuration parameters affect the logical repworker, but previously only wal_receiver_status_interval was not mentionedas such parameter in the doc.Back-patch to v10 where logical rep was added.Author: Masahiko SawadaDiscussion:https://www.postgresql.org/message-id/CAD21AoBUnuH_UsnKXyPCsCR7EAMamW0sSb6a7=WgiQRpnMAp5w@mail.gmail.com
1 parentde0aca6 commit2f8d636

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

‎doc/src/sgml/config.sgml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3410,7 +3410,8 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
34103410
</para>
34113411

34123412
<para>
3413-
Note that <varname>wal_receiver_timeout</varname> and
3413+
Note that <varname>wal_receiver_timeout</varname>,
3414+
<varname>wal_receiver_status_interval</varname> and
34143415
<varname>wal_retrieve_retry_interval</varname> configuration parameters
34153416
affect the logical replication workers as well.
34163417
</para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp