From 6fcaaf29dad233ceca67f31115dc75342a433e79 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 21 Aug 2005 03:39:37 +0000 Subject: Minor GUC cleanups: document krb_server_hostname and custom_variable_classes in postgresql.conf.sample, mark custom_variable_classes as SIGHUP not POSTMASTER to agree with the documentation (I can't see a reason it has to be POSTMASTER so I think the docs are right). --- doc/src/sgml/runtime.sgml | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index efb46060d96..0966b5105e5 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -1027,20 +1027,6 @@ SET ENABLE_SEQSCAN TO OFF; - - krb_caseins_users (boolean) - - krb_caseins_users configuration parameter - - - - Sets if Kerberos usernames should be treated case-insensitive. - The default is off (case sensitive). This parameter - can only be set at server start. - - - - krb_server_hostname (string) @@ -1061,6 +1047,20 @@ SET ENABLE_SEQSCAN TO OFF; + + krb_caseins_users (boolean) + + krb_caseins_users configuration parameter + + + + Sets if Kerberos usernames should be treated case-insensitively. + The default is off (case sensitive). This parameter + can only be set at server start. + + + + db_user_namespace (boolean) @@ -1068,13 +1068,13 @@ SET ENABLE_SEQSCAN TO OFF; - This allows per-database user names. It is off by default. + This enables per-database user names. It is off by default. If this is on, you should create users as username@dbname. When username is passed by a connecting client, - @ and the database name is appended to the user + @ and the database name are appended to the user name and that database-specific user name is looked up by the server. Note that when you create users with names containing @ within the SQL environment, you will need to -- cgit v1.2.3