From b66cbc1fa26aebfcfecbfff7c92d804d083af843 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 15 Apr 2002 22:33:21 +0000 Subject: 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. --- doc/src/sgml/runtime.sgml | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 2b0a4ad6349..babb95a4cd9 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -1231,10 +1231,8 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' 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 pg_catalog if the search - path list is empty. (Note that users do not normally have - permission to write in 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. -- cgit v1.2.3