doc: Note that CREATE MATERIALIZED VIEW restricts search_path.
Since v17, CREATE MATERIALIZED VIEW has set search_path to "pg_catalog, pg_temp" while running the query. The docs for the other commands that restrict search_path mention it, but the page for CREATE MATERIALIZED VIEW does not. Fix that. Oversight in commit 4b74ebf726. Author: Yugo Nagata Reviewed-by: Jeff Davis Discussion: https://postgr.es/m/20240805160502.d2a4975802a832b1e04afb80%40sraoss.co.jp Backpatch-through: 17
This commit is contained in:
parent
a3179ab692
commit
d8ebcac547
@ -143,7 +143,9 @@ CREATE MATERIALIZED VIEW [ IF NOT EXISTS ] <replaceable>table_name</replaceable>
|
||||
A <link linkend="sql-select"><command>SELECT</command></link>, <link linkend="sql-table"><command>TABLE</command></link>,
|
||||
or <link linkend="sql-values"><command>VALUES</command></link> command. This query will run within a
|
||||
security-restricted operation; in particular, calls to functions that
|
||||
themselves create temporary tables will fail.
|
||||
themselves create temporary tables will fail. Also, while the query is
|
||||
running, the <xref linkend="guc-search-path"/> is temporarily changed to
|
||||
<literal>pg_catalog, pg_temp</literal>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
Loading…
x
Reference in New Issue
Block a user