Last-minute updates for release notes.

Security: CVE-2021-3677

diff --git a/doc/src/sgml/release-11.sgml b/doc/src/sgml/release-11.sgml
index c9870804424b23505ec4bcaf160a41d95209025e..3b2db9421e6525474a55836a771174eafc91b8aa 100644 (file)
--- a/doc/src/sgml/release-11.sgml
+++ b/doc/src/sgml/release-11.sgml
@@ -35,6 +35,30 @@
 
     <listitem>
 <!--
+Author: Tom Lane <tgl@sss.pgh.pa.us>
+Branch: master Release: REL_14_BR [6ee41a301] 2021-05-31 12:03:00 -0400
+Branch: REL_13_STABLE [fe6f63286] 2021-05-31 12:03:00 -0400
+Branch: REL_12_STABLE [6f9e7f21f] 2021-05-31 12:03:00 -0400
+Branch: REL_11_STABLE [fe194f731] 2021-05-31 12:03:00 -0400
+-->
+     <para>
+      Fix mis-planning of repeated application of a projection step
+      (Tom Lane)
+     </para>
+
+     <para>
+      The planner could create an incorrect plan in cases where two
+      ProjectionPaths were stacked on top of each other.  The only known
+      way to trigger that situation involves parallel sort operations, but
+      there may be other instances.  The result would be crashes or
+      incorrect query results.
+      Disclosure of server memory contents is also possible.
+      (CVE-2021-3677)
+     </para>
+    </listitem>
+
+    <listitem>
+<!--
 Author: Michael Paquier <michael@paquier.xyz>
 Branch: master Release: REL_14_BR [01e6f1a84] 2021-05-25 10:10:09 +0900
 Branch: REL_13_STABLE [a23c0b00f] 2021-05-25 10:11:13 +0900
@@ -553,28 +577,6 @@ Branch: REL9_6_STABLE [85ec6c322] 2021-07-27 15:44:12 -0400
 
     <listitem>
 <!--
-Author: Tom Lane <tgl@sss.pgh.pa.us>
-Branch: master Release: REL_14_BR [6ee41a301] 2021-05-31 12:03:00 -0400
-Branch: REL_13_STABLE [fe6f63286] 2021-05-31 12:03:00 -0400
-Branch: REL_12_STABLE [6f9e7f21f] 2021-05-31 12:03:00 -0400
-Branch: REL_11_STABLE [fe194f731] 2021-05-31 12:03:00 -0400
--->
-     <para>
-      Fix mis-planning of repeated application of a projection step
-      (Tom Lane)
-     </para>
-
-     <para>
-      The planner could create an incorrect plan in cases where two
-      ProjectionPaths were stacked on top of each other.  The only known
-      way to trigger that situation involves parallel sort operations, but
-      there may be other instances.  The result would be crashes or
-      incorrect query results.
-     </para>
-    </listitem>
-
-    <listitem>
-<!--
 Author: Robert Haas <rhaas@postgresql.org>
 Branch: master Release: REL_14_BR [caba8f0d4] 2021-06-09 16:17:00 -0400
 Branch: REL_13_STABLE [082656429] 2021-06-09 16:17:13 -0400