Doc: update 4.1 release note.

For these commits:  2019-05-27 [33df0d33], 2019-08-08 [3922c12c].

diff --git a/doc/src/sgml/release-4.1.sgml b/doc/src/sgml/release-4.1.sgml
index 6d6f4436ac60d97c75c4a8489d3a071c61651387..a871b0e5beba2540c4f789cecad7021247d8332b 100644 (file)
--- a/doc/src/sgml/release-4.1.sgml
+++ b/doc/src/sgml/release-4.1.sgml
@@ -580,6 +580,37 @@
     </para>
    </listitem>
 
+   <listitem>
+    <!--
+    2019-05-27 [33df0d33]
+    2019-08-08 [3922c12c]
+    -->
+    <para>
+     Resign the master watchdog node from master responsibilities if
+     the primary backend node gets into quarantine state on that. (Muhammd Usama)
+    </para>
+    <para>
+     By doing this, we could avoid the situation on which there's no
+     primary <productname>PostgreSQL</productname> server exists.  To
+     implement this, make the master/coordinator watchdog node resign
+     from its status if it fails to get the consensus for the
+     quarantined primary node failover, within
+     FAILOVER_COMMAND_FINISH_TIMEOUT(15) seconds.
+    </para>
+    <para>
+     When the watchdog master resigns, because of quarantined primary
+     node its wd_priority is decreased to (-1), so that it should get
+     the least preference in the next election for the
+     master/coordinator node selection. And once the election is
+     concluded the wd_priority for the node gets restored to the
+     original configured value.
+    </para>
+    <para>
+     In case of failed consensus for standby node failover no action
+     is taken.
+    </para>
+   </listitem>
+
    <listitem>
     <!--
     2019-01-27 [f03ebdba]