1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00

Adjust rules for search_path so that pg_catalog is never implicitly

selected as the creation target namespace; to make that happen, you
must explicitly set search_path that way.  This makes initdb a hair
more complex but seems like a good safety feature.
This commit is contained in:
Tom Lane
2002-04-15 22:33:21 +00:00
parent c2f1e93aeb
commit b66cbc1fa2
3 changed files with 43 additions and 36 deletions

View File

@ -1,5 +1,5 @@
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.112 2002/04/03 05:39:29 petere Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.113 2002/04/15 22:33:20 tgl Exp $
-->
<Chapter Id="runtime">
@ -1231,10 +1231,8 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
<para>
When objects are created without specifying a particular target
namespace, they will be placed in the first namespace listed
in the search path, or in <literal>pg_catalog</> if the search
path list is empty. (Note that users do not normally have
permission to write in <literal>pg_catalog</>, so an empty search
path is not a very useful setting.)
in the search path. An error is reported if the search path is
empty.
</para>
<para>