Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitf34f0e4

Browse files
committed
Last-minute updates for release notes.
The set of functions that need parallel-safety adjustments isn't thesame 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 parentb56d5f2 commitf34f0e4

File tree

5 files changed

+44
-33
lines changed

5 files changed

+44
-33
lines changed

‎doc/src/sgml/release-10.sgml‎

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -106,10 +106,12 @@ Branch: REL9_3_STABLE [485857d44] 2018-03-30 18:14:51 -0400
106106
installations will continue to contain the incorrect markings.
107107
Practical use of these functions seems to pose little hazard, but in
108108
case of trouble, it can be fixed by manually updating these
109-
functions' <structname>pg_proc</structname> entries. (Note that that
110-
will need to be done in each database of the installation.) Another
111-
option is to <application>pg_upgrade</application> the database to a
112-
version containing the corrected initial data.
109+
functions' <structname>pg_proc</structname> entries, for example
110+
<literal>ALTER FUNCTION pg_catalog.query_to_xml(text, boolean,
111+
boolean, text) VOLATILE</literal>. (Note that that will need to be
112+
done in each database of the installation.) Another option is
113+
to <application>pg_upgrade</application> the database to a version
114+
containing the corrected initial data.
113115
</para>
114116
</listitem>
115117

@@ -146,10 +148,12 @@ Branch: REL9_6_STABLE [91d82317d] 2018-03-30 18:14:51 -0400
146148
incorrect markings. Practical use of these functions seems to pose
147149
little hazard unless <varname>force_parallel_mode</varname> is turned
148150
on. In case of trouble, it can be fixed by manually updating these
149-
functions' <structname>pg_proc</structname> entries. (Note that that
150-
will need to be done in each database of the installation.) Another
151-
option is to <application>pg_upgrade</application> the database to a
152-
version containing the corrected initial data.
151+
functions' <structname>pg_proc</structname> entries, for example
152+
<literal>ALTER FUNCTION pg_catalog.brin_summarize_new_values(regclass)
153+
PARALLEL UNSAFE</literal>. (Note that that will need to be done in
154+
each database of the installation.) Another option is
155+
to <application>pg_upgrade</application> the database to a version
156+
containing the corrected initial data.
153157
</para>
154158
</listitem>
155159

‎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)
[8]ページ先頭
©2009-2025 Movatter.jp