From e71d9f6951fa61f386bebe3c97735a80def8a1e2 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 7 May 2018 13:13:27 -0400 Subject: [PATCH] Last-minute updates for release notes. The set of functions that need parallel-safety adjustments isn't the same in 9.6 as 10, so I shouldn't have blindly back-patched that list. Adjust as needed. Also, provide examples of the commands to issue. --- doc/src/sgml/release-9.3.sgml | 10 ++++++---- doc/src/sgml/release-9.4.sgml | 10 ++++++---- doc/src/sgml/release-9.5.sgml | 10 ++++++---- doc/src/sgml/release-9.6.sgml | 27 ++++++++++++++------------- 4 files changed, 32 insertions(+), 25 deletions(-) diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml index 2bab389444..054ef1c37f 100644 --- a/doc/src/sgml/release-9.3.sgml +++ b/doc/src/sgml/release-9.3.sgml @@ -59,10 +59,12 @@ installations will continue to contain the incorrect markings. Practical use of these functions seems to pose little hazard, but in case of trouble, it can be fixed by manually updating these - functions' pg_proc entries. (Note that that - will need to be done in each database of the installation.) Another - option is to pg_upgrade the database to a - version containing the corrected initial data. + functions' pg_proc entries, for example + ALTER FUNCTION pg_catalog.query_to_xml(text, boolean, + boolean, text) VOLATILE. (Note that that will need to be + done in each database of the installation.) Another option is + to pg_upgrade the database to a version + containing the corrected initial data. diff --git a/doc/src/sgml/release-9.4.sgml b/doc/src/sgml/release-9.4.sgml index 67d3f2e3a3..d368990a84 100644 --- a/doc/src/sgml/release-9.4.sgml +++ b/doc/src/sgml/release-9.4.sgml @@ -59,10 +59,12 @@ installations will continue to contain the incorrect markings. Practical use of these functions seems to pose little hazard, but in case of trouble, it can be fixed by manually updating these - functions' pg_proc entries. (Note that that - will need to be done in each database of the installation.) Another - option is to pg_upgrade the database to a - version containing the corrected initial data. + functions' pg_proc entries, for example + ALTER FUNCTION pg_catalog.query_to_xml(text, boolean, + boolean, text) VOLATILE. (Note that that will need to be + done in each database of the installation.) Another option is + to pg_upgrade the database to a version + containing the corrected initial data. diff --git a/doc/src/sgml/release-9.5.sgml b/doc/src/sgml/release-9.5.sgml index 99fc9645a4..4c19c342c8 100644 --- a/doc/src/sgml/release-9.5.sgml +++ b/doc/src/sgml/release-9.5.sgml @@ -59,10 +59,12 @@ installations will continue to contain the incorrect markings. Practical use of these functions seems to pose little hazard, but in case of trouble, it can be fixed by manually updating these - functions' pg_proc entries. (Note that that - will need to be done in each database of the installation.) Another - option is to pg_upgrade the database to a - version containing the corrected initial data. + functions' pg_proc entries, for example + ALTER FUNCTION pg_catalog.query_to_xml(text, boolean, + boolean, text) VOLATILE. (Note that that will need to be + done in each database of the installation.) Another option is + to pg_upgrade the database to a version + containing the corrected initial data. diff --git a/doc/src/sgml/release-9.6.sgml b/doc/src/sgml/release-9.6.sgml index 4165287057..847889c51d 100644 --- a/doc/src/sgml/release-9.6.sgml +++ b/doc/src/sgml/release-9.6.sgml @@ -91,10 +91,12 @@ installations will continue to contain the incorrect markings. Practical use of these functions seems to pose little hazard, but in case of trouble, it can be fixed by manually updating these - functions' pg_proc entries. (Note that that - will need to be done in each database of the installation.) Another - option is to pg_upgrade the database to a - version containing the corrected initial data. + functions' pg_proc entries, for example + ALTER FUNCTION pg_catalog.query_to_xml(text, boolean, + boolean, text) VOLATILE. (Note that that will need to be + done in each database of the installation.) Another option is + to pg_upgrade the database to a version + containing the corrected initial data. @@ -107,15 +109,12 @@ The functions brin_summarize_new_values, - brin_summarize_range, - brin_desummarize_range, gin_clean_pending_list, cursor_to_xml, cursor_to_xmlschema, ts_rewrite, - ts_stat, - binary_upgrade_create_empty_extension, and - pg_import_system_collations + ts_stat, and + binary_upgrade_create_empty_extension should be marked parallel-unsafe; some because they perform database modifications directly, and others because they execute user-supplied queries that might do so. They were marked parallel-restricted @@ -125,10 +124,12 @@ incorrect markings. Practical use of these functions seems to pose little hazard unless force_parallel_mode is turned on. In case of trouble, it can be fixed by manually updating these - functions' pg_proc entries. (Note that that - will need to be done in each database of the installation.) Another - option is to pg_upgrade the database to a - version containing the corrected initial data. + functions' pg_proc entries, for example + ALTER FUNCTION pg_catalog.brin_summarize_new_values(regclass) + PARALLEL UNSAFE. (Note that that will need to be done in + each database of the installation.) Another option is + to pg_upgrade the database to a version + containing the corrected initial data.