database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-08 22:02:03 +03:00
Code

Last-minute updates for release notes.

Browse Source 
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.
This commit is contained in:
Tom Lane 2018-05-07 13:13:27 -04:00
parent dc441d5c2d
commit d289dcfc39
2 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/release-9.3.sgml
View File

@ -59,10 +59,12 @@
installations will continue to contain the incorrect markings. installations will continue to contain the incorrect markings.
Practical use of these functions seems to pose little hazard, but in Practical use of these functions seems to pose little hazard, but in
case of trouble, it can be fixed by manually updating these case of trouble, it can be fixed by manually updating these
functions' <structname>pg_proc</structname> entries. (Note that that functions' <structname>pg_proc</structname> entries, for example
will need to be done in each database of the installation.) Another <literal>ALTER FUNCTION pg_catalog.query_to_xml(text, boolean,
option is to <application>pg_upgrade</application> the database to a boolean, text) VOLATILE</literal>. (Note that that will need to be
version containing the corrected initial data. done in each database of the installation.) Another option is
to <application>pg_upgrade</application> the database to a version
containing the corrected initial data.
</para> </para>
</listitem> </listitem>

10
doc/src/sgml/release-9.4.sgml
View File

@ -59,10 +59,12 @@
installations will continue to contain the incorrect markings. installations will continue to contain the incorrect markings.
Practical use of these functions seems to pose little hazard, but in Practical use of these functions seems to pose little hazard, but in
case of trouble, it can be fixed by manually updating these case of trouble, it can be fixed by manually updating these
functions' <structname>pg_proc</structname> entries. (Note that that functions' <structname>pg_proc</structname> entries, for example
will need to be done in each database of the installation.) Another <literal>ALTER FUNCTION pg_catalog.query_to_xml(text, boolean,
option is to <application>pg_upgrade</application> the database to a boolean, text) VOLATILE</literal>. (Note that that will need to be
version containing the corrected initial data. done in each database of the installation.) Another option is
to <application>pg_upgrade</application> the database to a version
containing the corrected initial data.
</para> </para>
</listitem> </listitem>