Commit 122b9947 authored by Peter Eisentraut's avatar Peter Eisentraut

doc: Small wording change for clarity

From: Martín Marqués <martin@2ndquadrant.com>
parent 8a13d5e6
...@@ -528,7 +528,7 @@ $$ LANGUAGE plpgsql; ...@@ -528,7 +528,7 @@ $$ LANGUAGE plpgsql;
</para> </para>
<para> <para>
The same effect can be had by declaring one or more output parameters as The same effect can be obtained by declaring one or more output parameters as
polymorphic types. In this case the polymorphic types. In this case the
special <literal>$0</literal> parameter is not used; the output special <literal>$0</literal> parameter is not used; the output
parameters themselves serve the same purpose. For example: parameters themselves serve the same purpose. For example:
......
...@@ -753,7 +753,7 @@ SELECT * FROM dup(42); ...@@ -753,7 +753,7 @@ SELECT * FROM dup(42);
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 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 obtained
by forcing the temporary schema to be searched last. To do this, by forcing the temporary schema to be searched last. To do this,
write <literal>pg_temp</><indexterm><primary>pg_temp</><secondary>securing functions</></> as the last entry in <varname>search_path</>. write <literal>pg_temp</><indexterm><primary>pg_temp</><secondary>securing functions</></> as the last entry in <varname>search_path</>.
This function illustrates safe usage: This function illustrates safe usage:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment