diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml
index 2bab3894448..054ef1c37f1 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 67d3f2e3a37..d368990a841 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.