mirror of
https://github.com/postgres/postgres.git
synced 2025-05-28 05:21:27 +03:00
Fix newly-introduced documentation typo.
This commit is contained in:
parent
2bf97c9c4a
commit
a99381619e
@ -1,5 +1,5 @@
|
|||||||
<!--
|
<!--
|
||||||
$PostgreSQL: pgsql/doc/src/sgml/ref/create_function.sgml,v 1.67.2.1 2007/04/20 02:38:04 tgl Exp $
|
$PostgreSQL: pgsql/doc/src/sgml/ref/create_function.sgml,v 1.67.2.2 2007/04/23 16:52:58 neilc Exp $
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<refentry id="SQL-CREATEFUNCTION">
|
<refentry id="SQL-CREATEFUNCTION">
|
||||||
@ -483,7 +483,7 @@ SELECT * FROM dup(42);
|
|||||||
<xref linkend="guc-search-path"> should be set to exclude any schemas
|
<xref linkend="guc-search-path"> should be set to exclude any schemas
|
||||||
writable by untrusted users. This prevents
|
writable by untrusted users. This prevents
|
||||||
malicious users from creating objects that mask objects used by the
|
malicious users from creating objects that mask objects used by the
|
||||||
function. Particularly important is in this regard is the
|
function. Particularly important in this regard is the
|
||||||
temporary-table schema, which is searched first by default, and
|
temporary-table schema, which is searched first by default, and
|
||||||
is normally writable by anyone. A secure arrangement can be had
|
is normally writable by anyone. A secure arrangement can be had
|
||||||
by forcing the temporary schema to be searched last. To do this,
|
by forcing the temporary schema to be searched last. To do this,
|
||||||
|
Loading…
x
Reference in New Issue
Block a user