308308 When the node gets synchronized up to the minimum recovery
309309 lag, all the cluster nodes get locked for write transactions to allow the
310310 recovery process to finish. By default, the minimum recovery
311- lag is 100KB . You can change this value in the
311+ lag is 10MB . You can change this value in the
312312 <varname>multimaster.min_recovery_lag</varname> variable.
313313 </para>
314314 </listitem>
@@ -574,7 +574,7 @@ SELECT mtm.get_cluster_state();
574574 <para>
575575 <varname>multimaster.min_recovery_lag</varname> — sets the
576576 minimal WAL lag between the node to be restored and the current cluster state.
577- By default, <varname>multimaster.min_recovery_lag</varname> is set to 100KB .
577+ By default, <varname>multimaster.min_recovery_lag</varname> is set to 10MB .
578578 When the disconnected node is fast-forwarded up to the
579579 <varname>multimaster.min_recovery_lag</varname> threshold,
580580 <filename>multimaster</filename> stops all new commits to the
@@ -596,7 +596,7 @@ SELECT mtm.get_cluster_state();
596596 </itemizedlist>
597597 <para>
598598 By default, <varname>multimaster.max_recovery_lag</varname> is
599- set to 100MB . Setting
599+ set to 1GB . Setting
600600 <varname>multimaster.max_recovery_lag</varname> to a larger
601601 value increases the timeframe for automatic recovery, but
602602 requires more disk space for WAL collection.
@@ -1032,13 +1032,13 @@ pg_ctl -D <replaceable>datadir</replaceable> -l <replaceable>pg.log</replaceable
10321032 <varlistentry><term><varname>multimaster.min_recovery_lag</varname><indexterm><primary><varname>multimaster.min_recovery_lag</varname></primary></indexterm></term><listitem><para>
10331033 Minimal WAL lag
10341034 between the node to be restored and the current cluster state, in
1035- bytes . When this threshold is reached during node recovery, the
1035+ kB . When this threshold is reached during node recovery, the
10361036 cluster is locked for write transactions until the recovery is
1037- complete. </para><para>Default: 100000
1037+ complete. </para><para>Default: 10MB
10381038 </para></listitem></varlistentry>
10391039 <varlistentry><term><varname>multimaster.max_recovery_lag</varname><indexterm><primary><varname>multimaster.max_recovery_lag</varname></primary></indexterm></term><listitem><para>
10401040 Maximal WAL lag
1041- size, in bytes . When a node is disconnected from the cluster, other
1041+ size, in kB . When a node is disconnected from the cluster, other
10421042 nodes copy WALs for all new transactions into the replication slot of
10431043 this node. Upon reaching the
10441044 <varname>multimaster.max_recovery_lag</varname> value, the
@@ -1048,7 +1048,7 @@ pg_ctl -D <replaceable>datadir</replaceable> -l <replaceable>pg.log</replaceable
10481048 the data from one of the alive nodes using
10491049 <application>pg_basebackup</application> or a similar tool. If you set this
10501050 variable to zero, replication slot will not be dropped. </para><para>Default:
1051- 100000000
1051+ 1GB
10521052 </para></listitem></varlistentry>
10531053 <varlistentry id="ignore-tables-without-pk"><term><varname>multimaster.ignore_tables_without_pk</varname><indexterm><primary><varname>multimaster.ignore_tables_without_pk</varname></primary></indexterm></term><listitem><para>
10541054 Boolean.
@@ -1146,9 +1146,9 @@ pg_ctl -D <replaceable>datadir</replaceable> -l <replaceable>pg.log</replaceable
11461146 </indexterm>
11471147 </term>
11481148 <listitem>
1149- <para>The maximal size of transaction, in MB . When this threshold is reached, the transaction is written to the disk.
1149+ <para>The maximal size of transaction, in kB . When this threshold is reached, the transaction is written to the disk.
11501150 </para>
1151- <para>Default: 100
1151+ <para>Default: 100MB
11521152 </para>
11531153 </listitem>
11541154 </varlistentry>
0 commit comments