diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 4c2556c7817a99afb9cc7e3c59b7f4602b60a8ef..d14a123da0098b1a31a4fd7dcc94d66083dc20b8 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -1293,71 +1293,11 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' - SEARCH_PATH (string) - search_path - namespaces + KRB_SERVER_KEYFILE (string) - This variable specifies the order in which namespaces are searched - when an object (table, datatype, function, etc) is referenced by a - simple name with no schema component. When there are objects of - identical names in different namespaces, the one found first - in the search path is used. An object that is not in any of the - namespaces in the search path can only be referenced by specifying - its containing namespace with a qualified (dotted) name. - - - - The value for search_path has to be a comma-separated - list of namespace (schema) names. If one of the list items is - the special value $user, then the namespace - having the same name as the SESSION_USER is substituted, if there - is such a namespace. (If not, $user is ignored.) - - - - The system catalog namespace, pg_catalog, is always - searched, whether it is mentioned in the path or not. If it is - mentioned in the path then it will be searched in the specified - order. If pg_catalog is not in the path then it will - be searched before searching any of the path items. - It should also be noted that the temporary-table namespace, - pg_temp_nnn, is implicitly searched before any of - these. - - - - When objects are created without specifying a particular target - namespace, they will be placed in the first namespace listed - in the search path. An error is reported if the search path is - empty. - - - - The default value for this parameter is - '$user, public' (where the second part will be - ignored if there is no namespace named public). - This supports shared use of a database (where no users - have private namespaces, and all share use of public), - private per-user namespaces, and combinations of these. Other - effects can be obtained by altering the default search path - setting, either globally or per-user. - - - - By default, a newly created database will contain a world-writable - namespace named public, but no private namespaces. - The administrator may choose to restrict permissions on - public or even remove it, if that suits his purposes. - - - - The current effective value of the search path can be examined - via the SQL function current_schemas(). This is not - quite the same as examining the value of - search_path, since current_schemas() - shows how the requests appearing in search_path - were resolved. + Sets the location of the Kerberos server key file. See + for details. @@ -1416,16 +1356,6 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' - - KRB_SERVER_KEYFILE (string) - - - Sets the location of the Kerberos server key file. See - for details. - - - - LC_MESSAGES (string) @@ -1598,6 +1528,76 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' + + SEARCH_PATH (string) + search_path + namespaces + + + This variable specifies the order in which namespaces are searched + when an object (table, datatype, function, etc) is referenced by a + simple name with no schema component. When there are objects of + identical names in different namespaces, the one found first + in the search path is used. An object that is not in any of the + namespaces in the search path can only be referenced by specifying + its containing namespace with a qualified (dotted) name. + + + + The value for search_path has to be a comma-separated + list of namespace (schema) names. If one of the list items is + the special value $user, then the namespace + having the same name as the SESSION_USER is substituted, if there + is such a namespace. (If not, $user is ignored.) + + + + The system catalog namespace, pg_catalog, is always + searched, whether it is mentioned in the path or not. If it is + mentioned in the path then it will be searched in the specified + order. If pg_catalog is not in the path then it will + be searched before searching any of the path items. + It should also be noted that the temporary-table namespace, + pg_temp_nnn, is implicitly searched before any of + these. + + + + When objects are created without specifying a particular target + namespace, they will be placed in the first namespace listed + in the search path. An error is reported if the search path is + empty. + + + + The default value for this parameter is + '$user, public' (where the second part will be + ignored if there is no namespace named public). + This supports shared use of a database (where no users + have private namespaces, and all share use of public), + private per-user namespaces, and combinations of these. Other + effects can be obtained by altering the default search path + setting, either globally or per-user. + + + + By default, a newly created database will contain a world-writable + namespace named public, but no private namespaces. + The administrator may choose to restrict permissions on + public or even remove it, if that suits his purposes. + + + + The current effective value of the search path can be examined + via the SQL function current_schemas(). This is not + quite the same as examining the value of + search_path, since current_schemas() + shows how the requests appearing in search_path + were resolved. + + + + STATEMENT_TIMEOUT (integer)