doc: Put pg_temp into documentation index

Karl O. Pinc
This commit is contained in:
Peter Eisentraut 2012-11-17 18:08:13 -05:00
parent 67c03c6f3c
commit 6b6633ad6c
2 changed files with 2 additions and 2 deletions

View File

@ -4810,7 +4810,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
Likewise, the current session's temporary-table schema, Likewise, the current session's temporary-table schema,
<literal>pg_temp_<replaceable>nnn</></>, is always searched if it <literal>pg_temp_<replaceable>nnn</></>, is always searched if it
exists. It can be explicitly listed in the path by using the exists. It can be explicitly listed in the path by using the
alias <literal>pg_temp</>. If it is not listed in the path then alias <literal>pg_temp</><indexterm><primary>pg_temp</></>. If it is not listed in the path then
it is searched first (even before <literal>pg_catalog</>). However, it is searched first (even before <literal>pg_catalog</>). However,
the temporary schema is only searched for relation (table, view, the temporary schema is only searched for relation (table, view,
sequence, etc) and data type names. It is never searched for sequence, etc) and data type names. It is never searched for

View File

@ -684,7 +684,7 @@ SELECT * FROM dup(42);
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,
write <literal>pg_temp</> 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:
</para> </para>