database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-13 07:41:39 +03:00
Code Activity

Allow the logical_replication_mode to be used on the subscriber.

Browse Source 
Extend the existing developer option 'logical_replication_mode' to help
test the parallel apply of large transactions on the subscriber.

When set to 'buffered', the leader sends changes to parallel apply workers
via a shared memory queue. When set to 'immediate', the leader serializes
all changes to files and notifies the parallel apply workers to read and
apply them at the end of the transaction.

This helps in adding tests to cover the serialization code path in
parallel streaming mode.

Author: Hou Zhijie
Reviewed-by: Peter Smith, Kuroda Hayato, Sawada Masahiko, Amit Kapila
Discussion: https://postgr.es/m/CAA4eK1+wyN6zpaHUkCLorEWNx75MG0xhMwcFhvjqm2KURZEAGw@mail.gmail.com
This commit is contained in:
Amit Kapila
2023-02-02 08:15:18 +05:30
parent fb1a59de0c
commit 9f2213a7c5
6 changed files with 172 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
doc/src/sgml/config.sgml
View File

@ -11701,22 +11701,35 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
</term>
<listitem>
<para>
Allows streaming or serializing changes immediately in logical decoding.
The allowed values of <varname>logical_replication_mode</varname> are
<literal>buffered</literal> and <literal>immediate</literal>. When set
to <literal>immediate</literal>, stream each change if
The allowed values are <literal>buffered</literal> and
<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
publisher and subscriber:
</para>
<para>
On the publisher side, <varname>logical_replication_mode</varname>
allows streaming or serializing changes immediately in logical decoding.
When set to <literal>immediate</literal>, stream each change if the
<literal>streaming</literal> option (see optional parameters set by
<link linkend="sql-createsubscription"><command>CREATE SUBSCRIPTION</command></link>)
is enabled, otherwise, serialize each change. When set to
<literal>buffered</literal>, which is the default, decoding will stream
or serialize changes when <varname>logical_decoding_work_mem</varname>
is reached.
<literal>buffered</literal>, the decoding will stream or serialize
changes when <varname>logical_decoding_work_mem</varname> is reached.
</para>
<para>
This parameter is intended to be used to test logical decoding and
replication of large transactions for which otherwise we need to
generate the changes till <varname>logical_decoding_work_mem</varname>
is reached.
On the subscriber side, if the <literal>streaming</literal> option is set to
<literal>parallel</literal>, <varname>logical_replication_mode</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
workers via a shared memory queue. When set to
<literal>immediate</literal>, the leader serializes all changes to files
and notifies the parallel apply workers to read and apply them at the
end of the transaction.
</para>
</listitem>
</varlistentry>