From 5a072244919a92b2c757b2e3985191f02d674627 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 4 Sep 2016 13:19:54 -0400
Subject: [PATCH] Update release notes to mention need for ALTER EXTENSION
UPDATE.
Maybe we ought to make pg_upgrade do this for you, but it won't happen
in 9.6, so call out the need for it as a migration consideration.
---
doc/src/sgml/release-9.6.sgml | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/doc/src/sgml/release-9.6.sgml b/doc/src/sgml/release-9.6.sgml
index 895d88e7681..578c3d1fdb6 100644
--- a/doc/src/sgml/release-9.6.sgml
+++ b/doc/src/sgml/release-9.6.sgml
@@ -303,6 +303,26 @@ This commit is also listed under libpq and psql
</para>
</listitem>
+ <listitem>
+<!--
+2016-06-07 [a89b4b1be] Update citext extension for parallel query.
+and many others in the same vein
+-->
+ <para>
+ Update extension functions to be marked parallel-safe where
+ appropriate (Andreas Karlsson)
+ </para>
+
+ <para>
+ Many of the standard extensions have been updated to allow their
+ functions to be executed within parallel query worker processes.
+ These changes will not take effect in
+ databases <application>pg_upgrade</>'d from prior versions unless
+ you apply <command>ALTER EXTENSION UPDATE</> to each such extension
+ (in each database of a cluster).
+ </para>
+ </listitem>
+
</itemizedlist>
</sect2>
--
GitLab