From: Tom Lane Date: Mon, 7 May 2018 17:13:27 +0000 (-0400) Subject: Last-minute updates for release notes. X-Git-Tag: REL_11_BETA1~77 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f34f0e4c58a31e5edd3aa8a23e171fbcf7e01ff2;p=postgresql 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. --- diff --git a/doc/src/sgml/release-10.sgml b/doc/src/sgml/release-10.sgml index bdaeb95ec5..be37349ec2 100644 --- a/doc/src/sgml/release-10.sgml +++ b/doc/src/sgml/release-10.sgml @@ -106,10 +106,12 @@ Branch: REL9_3_STABLE [485857d44] 2018-03-30 18:14:51 -0400 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. @@ -146,10 +148,12 @@ Branch: REL9_6_STABLE [91d82317d] 2018-03-30 18:14:51 -0400 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. diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml index e8604f9954..4c063551d0 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 627eca168f..5c93f00e19 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 c646be6f9d..cf7db406f8 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 43e7073b98..541afa8ab1 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.