doc PG 17 relnotes: add missing commands for safe search path

Reported-by: Yugo NAGATA
Discussion: https://postgr.es/m/20240926141921.57d0b430fa53ac4389344847@sraoss.co.jp

Backpatch-through: 17 only

diff --git a/doc/src/sgml/release-17.sgml b/doc/src/sgml/release-17.sgml
index 8d433c9957da19e36d23c583b90fec0d43d58cad..3e4fe94a6463d8a9aebbd988ed738755fd230487 100644 (file)
--- a/doc/src/sgml/release-17.sgml
+++ b/doc/src/sgml/release-17.sgml
@@ -125,6 +125,8 @@
 <!--
 Author: Jeff Davis <jdavis@postgresql.org>
 2024-03-04 [2af07e2f7] Fix search_path to a safe value during maintenance opera
+Author: Jeff Davis <jdavis@postgresql.org>
+2024-07-16 [b4da732fd64] When creating materialized views, use REFRESH to load data.
 -->
 
     <listitem>
@@ -132,11 +134,14 @@ Author: Jeff Davis <jdavis@postgresql.org>
      Change functions to use a safe <xref linkend="guc-search-path"/>
      during maintenance operations (Jeff Davis)
      <ulink url="&commit_baseurl;2af07e2f7">&sect;</ulink>
+     <ulink url="&commit_baseurl;b4da732fd64">&sect;</ulink>
      </para>
 
      <para>
      This prevents maintenance operations (<command>ANALYZE</command>,
-     <command>CLUSTER</command>, <command>REFRESH
+     <command>CLUSTER</command>, <command>CREATE
+     INDEX</command>, <command>CREATE
+     MATERIALIZED VIEW</command>, <command>REFRESH
      MATERIALIZED VIEW</command>, <command>REINDEX</command>,
      or <command>VACUUM</command>) from performing unsafe access.
      Functions used by expression indexes and materialized views that