Doc: update v10 release notes through today.

doc/src/sgml/release-10.sgml

@@ -6,7 +6,7 @@
 
   <formalpara>
    <title>Release date:</title>
-   <para>2017-??-?? (current as of 2017-07-09, commit 3381898f9)</para>
+   <para>2017-??-?? (current as of 2017-08-05, commit eccead9ed)</para>
   </formalpara>
 
   <sect2>
@@ -416,9 +416,10 @@
      </para>
 
      <para>
-      This replaces the hardcoded, undocumented <filename>dh1024.pem</>
+      This replaces the hardcoded, undocumented file
-      filename. Note that <filename>dh1024.pem</> is no longer used by default;
+      name <filename>dh1024.pem</>.  Note that <filename>dh1024.pem</> is
-      you must set the option to use custom DH parameters.
+      no longer examined by default; you must set this option to use custom
+      DH parameters.
      </para>
     </listitem>
 
@@ -427,19 +428,30 @@
 2017-07-31 [c0a15e07c] Always use 2048 bit DH parameters for OpenSSL ephemeral
 -->
      <para>
-      Increase the size of DH parameters used for OpenSSL ephemeral DH ciphers
+      Increase the size of the default DH parameters used for OpenSSL
-      to 2048 bits (Heikki Linnakangas)
+      ephemeral DH ciphers to 2048 bits (Heikki Linnakangas)
      </para>
 
      <para>
-      The size of the compiled-in DH parameters has been increased from 1024
+      The size of the compiled-in DH parameters has been increased from
-      to 2048 bits, making DH key exchange more resistent to a brute-force
+      1024 to 2048 bits, making DH key exchange more resistant to
-      attack. However, some old SSL implementations, notably some revisions of
+      brute-force attacks.  However, some old SSL implementations, notably
-      Java Runtime Environment version 6, will not accept DH parameters longer
+      some revisions of Java Runtime Environment version 6, will not accept
-      than 1024 bits, and will not be able to connect over SSL. As a
+      DH parameters longer than 1024 bits, and hence will not be able to
-      work-around, you can use custom 1024-bit DH parameters, instead of the
+      connect over SSL.  If it's necessary to support such old clients, you
-      compiled-in defaults. See <xref linkend="guc-ssl-dh-params-file"> for
+      can use custom 1024-bit DH parameters instead of the compiled-in
-      information on using custom DH parameters.
+      defaults.  See <xref linkend="guc-ssl-dh-params-file">.
+     </para>
+    </listitem>
+
+    <listitem>
+<!--
+2017-08-04 [c30f1770a] Apply ALTER ... SET NOT NULL recursively in ALTER ... AD
+-->
+     <para>
+      When <command>ALTER TABLE ... ADD PRIMARY KEY</> marks
+      columns <literal>NOT NULL</>, that change now propagates to
+      inheritance child tables as well (Michael Paquier)
      </para>
     </listitem>
 
@@ -887,10 +899,11 @@
       <listitem>
 <!--
 2017-03-25 [b8d7f053c] Faster expression evaluation and targetlist projection.
+2017-07-30 [cc9f08b6b] Move ExecProcNode from dispatch to function pointer base
 -->
        <para>
-        Reduce expression evaluation overhead during query execution (Andres
+        Reduce expression evaluation overhead during query execution,
-        Freund)
+        as well as plan node calling overhead (Andres Freund)
        </para>
 
        <para>
@@ -2109,12 +2122,12 @@
 <!--
 2016-11-03 [274bb2b38] libpq: Allow connection strings and URIs to specify mult
 2017-05-19 [5f374fe7a] libpq: Try next host if one of them times out.
+2017-07-10 [7b02ba62e] Allow multiple hostaddrs to go with multiple hostnames.
 -->
       <para>
-       Allow specification of <link
+       Allow specification of <link linkend="libpq-connect-host">multiple
-       linkend="libpq-connect-host">multiple host names</> in libpq
+       host names or addresses</> in libpq connection strings and URIs
-       connection strings and URIs
+       (Robert Haas, Heikki Linnakangas)
-       (Robert Haas)
       </para>
 
       <para>