Skip to content

Commit e71d9f6

Browse files
committed
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.
1 parent 2a77198 commit e71d9f6

File tree

4 files changed

+32
-25
lines changed

4 files changed

+32
-25
lines changed

doc/src/sgml/release-9.3.sgml

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -59,10 +59,12 @@
5959
installations will continue to contain the incorrect markings.
6060
Practical use of these functions seems to pose little hazard, but in
6161
case of trouble, it can be fixed by manually updating these
62-
functions' <structname>pg_proc</structname> entries. (Note that that
63-
will need to be done in each database of the installation.) Another
64-
option is to <application>pg_upgrade</application> the database to a
65-
version containing the corrected initial data.
62+
functions' <structname>pg_proc</structname> entries, for example
63+
<literal>ALTER FUNCTION pg_catalog.query_to_xml(text, boolean,
64+
boolean, text) VOLATILE</literal>. (Note that that will need to be
65+
done in each database of the installation.) Another option is
66+
to <application>pg_upgrade</application> the database to a version
67+
containing the corrected initial data.
6668
</para>
6769
</listitem>
6870

doc/src/sgml/release-9.4.sgml

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -59,10 +59,12 @@
5959
installations will continue to contain the incorrect markings.
6060
Practical use of these functions seems to pose little hazard, but in
6161
case of trouble, it can be fixed by manually updating these
62-
functions' <structname>pg_proc</structname> entries. (Note that that
63-
will need to be done in each database of the installation.) Another
64-
option is to <application>pg_upgrade</application> the database to a
65-
version containing the corrected initial data.
62+
functions' <structname>pg_proc</structname> entries, for example
63+
<literal>ALTER FUNCTION pg_catalog.query_to_xml(text, boolean,
64+
boolean, text) VOLATILE</literal>. (Note that that will need to be
65+
done in each database of the installation.) Another option is
66+
to <application>pg_upgrade</application> the database to a version
67+
containing the corrected initial data.
6668
</para>
6769
</listitem>
6870

doc/src/sgml/release-9.5.sgml

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -59,10 +59,12 @@
5959
installations will continue to contain the incorrect markings.
6060
Practical use of these functions seems to pose little hazard, but in
6161
case of trouble, it can be fixed by manually updating these
62-
functions' <structname>pg_proc</structname> entries. (Note that that
63-
will need to be done in each database of the installation.) Another
64-
option is to <application>pg_upgrade</application> the database to a
65-
version containing the corrected initial data.
62+
functions' <structname>pg_proc</structname> entries, for example
63+
<literal>ALTER FUNCTION pg_catalog.query_to_xml(text, boolean,
64+
boolean, text) VOLATILE</literal>. (Note that that will need to be
65+
done in each database of the installation.) Another option is
66+
to <application>pg_upgrade</application> the database to a version
67+
containing the corrected initial data.
6668
</para>
6769
</listitem>
6870

doc/src/sgml/release-9.6.sgml

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -91,10 +91,12 @@
9191
installations will continue to contain the incorrect markings.
9292
Practical use of these functions seems to pose little hazard, but in
9393
case of trouble, it can be fixed by manually updating these
94-
functions' <structname>pg_proc</structname> entries. (Note that that
95-
will need to be done in each database of the installation.) Another
96-
option is to <application>pg_upgrade</application> the database to a
97-
version containing the corrected initial data.
94+
functions' <structname>pg_proc</structname> entries, for example
95+
<literal>ALTER FUNCTION pg_catalog.query_to_xml(text, boolean,
96+
boolean, text) VOLATILE</literal>. (Note that that will need to be
97+
done in each database of the installation.) Another option is
98+
to <application>pg_upgrade</application> the database to a version
99+
containing the corrected initial data.
98100
</para>
99101
</listitem>
100102

@@ -107,15 +109,12 @@
107109
<para>
108110
The functions
109111
<function>brin_summarize_new_values</function>,
110-
<function>brin_summarize_range</function>,
111-
<function>brin_desummarize_range</function>,
112112
<function>gin_clean_pending_list</function>,
113113
<function>cursor_to_xml</function>,
114114
<function>cursor_to_xmlschema</function>,
115115
<function>ts_rewrite</function>,
116-
<function>ts_stat</function>,
117-
<function>binary_upgrade_create_empty_extension</function>, and
118-
<function>pg_import_system_collations</function>
116+
<function>ts_stat</function>, and
117+
<function>binary_upgrade_create_empty_extension</function>
119118
should be marked parallel-unsafe; some because they perform database
120119
modifications directly, and others because they execute user-supplied
121120
queries that might do so. They were marked parallel-restricted
@@ -125,10 +124,12 @@
125124
incorrect markings. Practical use of these functions seems to pose
126125
little hazard unless <varname>force_parallel_mode</varname> is turned
127126
on. In case of trouble, it can be fixed by manually updating these
128-
functions' <structname>pg_proc</structname> entries. (Note that that
129-
will need to be done in each database of the installation.) Another
130-
option is to <application>pg_upgrade</application> the database to a
131-
version containing the corrected initial data.
127+
functions' <structname>pg_proc</structname> entries, for example
128+
<literal>ALTER FUNCTION pg_catalog.brin_summarize_new_values(regclass)
129+
PARALLEL UNSAFE</literal>. (Note that that will need to be done in
130+
each database of the installation.) Another option is
131+
to <application>pg_upgrade</application> the database to a version
132+
containing the corrected initial data.
132133
</para>
133134
</listitem>
134135

0 commit comments

Comments
 (0)