Incorporate feedback into 20180510 release and update language.

diff --git a/update_releases/current/20180510securityrelease.md b/update_releases/current/20180510securityrelease.md
index 6e9208e5293bd01af28d2db65cb0d0ee46027ee3..5782d3a3ef651811e64176380cb7bb3ae319b9e8 100644 (file)
--- a/update_releases/current/20180510securityrelease.md
+++ b/update_releases/current/20180510securityrelease.md
@@ -1,9 +1,9 @@
 2018-05-10 Security Update Release
 ==================================
 
-The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.4, 9.6.9, 9.5.13, 9.4.18, 9.3.23. This release fixes one security issue as well as fixes for bugs reported over the last three months.  Users who have installed the adminpack extension in a PostgreSQL 9.6 or 10 release should update as soon as possible.  Other users should plan to update at the next convenient downtime.
+The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.4, 9.6.9, 9.5.13, 9.4.18, 9.3.23. This release fixes one security issue as well as several bugs reported over the last three months.  Users should plan to update at the next convenient downtime.
 
-Please see the "Updating" section for post-installation steps for the security fix and the "incorrect volatility and parallel-safety" markings fix.
+Please see the "Updating" section for post-installation steps for the security fix and the "incorrect volatility and parallel-safety markings" fix.
 
 Please note that PostgreSQL changed its versioning scheme with the release of version 10.0, so updating to version 10.4 from 10.0, 10.1, 10.2, or 10.3 is considered a minor update.
 
@@ -21,11 +21,11 @@ Bug Fixes and Improvements
 
 This update also fixes over 50 bugs reported in the last several months. Some of these issues affect only version 10, but many affect all supported versions.  These fixes include:
 
-* Fix incorrect volatility and parallel-safety markings on several built-in functions to ensure correct query planning optimizations. [PLEASE CHECK LIST OF FUNC]
-* Several fixes for partitioning, including potential crashes and allowing TRULE and FALSE to be used as partition bounds
-* Fix where a new TOAST value could be assigned to an dead-but-not-yet-vacuumed TOAST OID, which would result in an error similar to "unexpected chunk number 0 (expected 1) for toast value nnnnn"
-* Fix "CREATE TABLE ... LIKE" with bigint identity columns on 32-bit platforms.
-* Fix memory leak within the runtime of a query that repeatedly executes hash joins.
+* Fix incorrect volatility and parallel-safety markings on several built-in functions to ensure correct query planning optimizations
+* Several fixes for partitioning, including potential crashes as well as allowing TRUE and FALSE to be used as partition bounds
+* Fix where a new TOAST value could be assigned to a dead-but-not-yet-vacuumed TOAST OID, which would result in an error similar to "unexpected chunk number 0 (expected 1) for toast value nnnnn"
+* Fix "CREATE TABLE ... LIKE" with bigint identity columns on 32-bit platforms
+* Fix memory leak within the runtime of a query that repeatedly executes hash joins
 * Several crash fixes around queries using GROUPING SET
 * Avoid failure if a query-cancel or session-termination interrupt occurs while committing a prepared transaction
 * Reduce locking during autovacuum worker scheduling, which prevents loss of potential worker concurrency
@@ -46,7 +46,7 @@ This update also contains tzdata release 2018d, with updates for Palestine and A
 Updating
 --------
 
-All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use pg\_upgrade in order to apply this update release (though for this release, please see the note about "volatility and parallel-safety markings"); you may simply shut down PostgreSQL and update its binaries.
+All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use pg\_upgrade to apply this update release (though for this release, please see the note about "volatility and parallel-safety markings"); you may simply shut down PostgreSQL and update its binaries.
 
 Users who have skipped one or more update releases may need to run additional, post-update steps; please see the release notes for earlier versions for details.
 
@@ -83,12 +83,34 @@ Post-Installation Steps for Function Markings
 
 If you use any of the above functions, you can update the markings in the following ways:
 
-1. Update the markings manually in the "pg\_proc" table in each database you use these functions
-2. Run a pg\_upgrade to a version containing the correct marking data (e.g. 10.4 and above)
+1\. Update the markings manually in the "pg\_proc" table in each database you use these functions. You can achieve this by executing the following commands as a database superuser:
+
+```
+/* Functions that should be marked "volatile" */
+ALTER FUNCTION pg_catalog.cursor_to_xml(refcursor, int, boolean, boolean, text) VOLATILE;
+ALTER FUNCTION pg_catalog.cursor_to_xmlschema(refcursor, boolean, boolean, text) VOLATILE;
+ALTER FUNCTION pg_catalog.query_to_xml(text, boolean, boolean, text) VOLATILE;
+ALTER FUNCTION pg_catalog.query_to_xml_and_xmlschema(text, boolean, boolean, text) VOLATILE;
+ALTER FUNCTION pg_catalog.query_to_xmlschema(text, boolean, boolean, text) VOLATILE;
+/* Functions that should be marked "parallel-unsafe" */
+ALTER FUNCTION pg_catalog.binary_upgrade_create_empty_extension(text, text, bool, text, _oid, _text, _text) PARALLEL UNSAFE;
+ALTER FUNCTION pg_catalog.brin_desummarize_range(regclass, bigint) PARALLEL UNSAFE;
+ALTER FUNCTION pg_catalog.brin_summarize_new_values(regclass) PARALLEL UNSAFE;
+ALTER FUNCTION pg_catalog.brin_summarize_range(regclass, bigint) PARALLEL UNSAFE;
+ALTER FUNCTION pg_catalog.cursor_to_xml(refcursor, int, boolean, boolean, text) PARALLEL UNSAFE;
+ALTER FUNCTION pg_catalog.cursor_to_xmlschema(refcursor, boolean, boolean, text) PARALLEL UNSAFE;
+ALTER FUNCTION pg_catalog.gin_clean_pending_list(regclass) PARALLEL UNSAFE;
+ALTER FUNCTION pg_catalog.pg_import_system_collations(regnamespace) PARALLEL UNSAFE;
+ALTER FUNCTION pg_catalog.ts_rewrite(tsquery, tsquery, tsquery) PARALLEL UNSAFE;
+ALTER FUNCTION pg_catalog.ts_stat(text) PARALLEL UNSAFE;
+ALTER FUNCTION pg_catalog.ts_stat(text, text) PARALLEL UNSAFE;
+```
+
+2\. Run a pg\_upgrade to a version containing the correct marking data (e.g. 10.4 and above)
 
 Links
 -----
-* [Download](https://www.postgresql.org/download)
+* [Download](https://www.postgresql.org/download/)
 * [Release Notes](https://www.postgresql.org/docs/current/static/release.html)
 * [Security Page](https://www.postgresql.org/support/security/)
 * [Versioning Policy](https://www.postgresql.org/support/versioning/)