Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 035524b

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 d58aaf7 commit 035524b

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
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

0 commit comments

Comments
 (0)