diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2023-08-29 15:15:54 +0200 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2023-08-29 15:19:56 +0200 |
| commit | 63956bed7b10fb3bb5fe3f74250a33c9e226a921 (patch) | |
| tree | 3e3de96cfc63bc7b1c1addca137f8ee872f6cfd1 /doc/src | |
| parent | f347ec76e2a227e5c5b5065cce7adad16d58d209 (diff) | |
| download | postgresql-63956bed7b10fb3bb5fe3f74250a33c9e226a921.tar.gz postgresql-63956bed7b10fb3bb5fe3f74250a33c9e226a921.zip | |
Rename logical_replication_mode to debug_logical_replication_streaming
The logical_replication_mode GUC is intended for testing and debugging
purposes, but its current name may be misleading and encourage users to make
unnecessary changes.
To avoid confusion, renaming the GUC to a less misleading name
debug_logical_replication_streaming that casual users are less likely to mistakenly
assume needs to be modified in a regular logical replication setup.
Author: Hou Zhijie <houzj.fnst@cn.fujitsu.com>
Reviewed-by: Peter Smith <smithpb2250@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/d672d774-c44b-6fec-f993-793e744f169a%40eisentraut.org
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/config.sgml | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 11251fa05ea..694d667bf97 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -11712,10 +11712,10 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) </listitem> </varlistentry> - <varlistentry id="guc-logical-replication-mode" xreflabel="logical_replication_mode"> - <term><varname>logical_replication_mode</varname> (<type>enum</type>) + <varlistentry id="guc-debug-logical-replication-streaming" xreflabel="debug_logical_replication_streaming"> + <term><varname>debug_logical_replication_streaming</varname> (<type>enum</type>) <indexterm> - <primary><varname>logical_replication_mode</varname> configuration parameter</primary> + <primary><varname>debug_logical_replication_streaming</varname> configuration parameter</primary> </indexterm> </term> <listitem> @@ -11724,12 +11724,12 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) <literal>immediate</literal>. The default is <literal>buffered</literal>. This parameter is intended to be used to test logical decoding and replication of large transactions. The effect of - <varname>logical_replication_mode</varname> is different for the + <varname>debug_logical_replication_streaming</varname> is different for the publisher and subscriber: </para> <para> - On the publisher side, <varname>logical_replication_mode</varname> + On the publisher side, <varname>debug_logical_replication_streaming</varname> allows streaming or serializing changes immediately in logical decoding. When set to <literal>immediate</literal>, stream each change if the <link linkend="sql-createsubscription-with-streaming"><literal>streaming</literal></link> @@ -11742,7 +11742,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) <para> On the subscriber side, if the <literal>streaming</literal> option is set to - <literal>parallel</literal>, <varname>logical_replication_mode</varname> + <literal>parallel</literal>, <varname>debug_logical_replication_streaming</varname> can be used to direct the leader apply worker to send changes to the shared memory queue or to serialize all changes to the file. When set to <literal>buffered</literal>, the leader sends changes to parallel apply |