wal_keep_size_release_note_v1.patch

text/plain

Filename: wal_keep_size_release_note_v1.patch
Type: text/plain
Part: 0
Message: Re: max_slot_wal_keep_size and wal_keep_segments

Patch

Format: unified
Series: patch v1
File+
doc/src/sgml/release-13.sgml 22 0
diff --git a/doc/src/sgml/release-13.sgml b/doc/src/sgml/release-13.sgml
index 22363a186b..c3698c1401 100644
--- a/doc/src/sgml/release-13.sgml
+++ b/doc/src/sgml/release-13.sgml
@@ -209,6 +209,28 @@ Author: Fujii Masao <fujii@postgresql.org>
 
     <listitem>
 <!--
+Author: Fujii Masao <fujii@postgresql.org>
+2020-07-20 [f5dff45962] Rename wal_keep_segments to wal_keep_size.
+-->
+
+     <para>
+      Rename configuration parameter <varname>wal_keep_segments</varname>
+      to <xref linkend="guc-wal-keep-size"/> (Fujii Masao)
+     </para>
+
+     <para>
+      This allows how much WAL files to retain for the standby server,
+      to be specified by bytes instead of the number of files. If you
+      previously used <varname>wal_keep_segments</varname>,
+      the following formula will give you an approximately equivalent setting:
+<programlisting>
+wal_keep_size = wal_keep_segments * wal_segment_size (typically 16MB)
+</programlisting>
+     </para>
+    </listitem>
+
+    <listitem>
+<!--
 Author: Tom Lane <tgl@sss.pgh.pa.us>
 2020-03-05 [84eca14bc] Remove ancient hacks to ignore certain opclass names in
 -->