From: Bruce Momjian Date: Mon, 22 Mar 2010 14:56:09 +0000 (+0000) Subject: Re-order createuser and vacuumedb documentation options, for X-Git-Tag: REL9_0_ALPHA5~46 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=260d843d70e19e6d56bc6e2ad84d53cc5e31f377;p=postgresql Re-order createuser and vacuumedb documentation options, for consistency. Gabrielle (Roth) --- diff --git a/doc/src/sgml/ref/createuser.sgml b/doc/src/sgml/ref/createuser.sgml index 99582f8722..41e0bafd88 100644 --- a/doc/src/sgml/ref/createuser.sgml +++ b/doc/src/sgml/ref/createuser.sgml @@ -1,5 +1,5 @@ @@ -78,22 +78,12 @@ PostgreSQL documentation - - - - - The new user will be a superuser. - - - - - - - + + - The new user will not be a superuser. - This is the default. + Set a maximum number of connections for the new user. + The default is to set no limit. @@ -120,81 +110,81 @@ PostgreSQL documentation - - + + - The new user will be allowed to create new roles (that is, - this user will have CREATEROLE privilege). + Echo the commands that createuser generates + and sends to the server. - - + + - The new user will not be allowed to create new roles. - This is the default. + Encrypts the user's password stored in the database. If not + specified, the default password behavior is used. - - + + - The new user will be allowed to log in (that is, the user name - can be used as the initial session user identifier). + The new role will automatically inherit privileges of roles + it is a member of. This is the default. - - + + - The new user will not be allowed to log in. - (A role without login privilege is still useful as a means of - managing database permissions.) + The new role will not automatically inherit privileges of roles + it is a member of. - - + + - The new role will automatically inherit privileges of roles - it is a member of. + The new user will be allowed to log in (that is, the user name + can be used as the initial session user identifier). This is the default. - - + + - The new role will not automatically inherit privileges of roles - it is a member of. + The new user will not be allowed to log in. + (A role without login privilege is still useful as a means of + managing database permissions.) - - + + - Set a maximum number of connections for the new user. - The default is to set no limit. + Does not encrypt the user's password stored in the database. If + not specified, the default password behavior is used. @@ -212,34 +202,44 @@ PostgreSQL documentation - - + + - Encrypts the user's password stored in the database. If not - specified, the default password behavior is used. + The new user will be allowed to create new roles (that is, + this user will have CREATEROLE privilege). - - + + - Does not encrypt the user's password stored in the database. If - not specified, the default password behavior is used. + The new user will not be allowed to create new roles. + This is the default. - - + + - Echo the commands that createuser generates - and sends to the server. + The new user will be a superuser. + + + + + + + + + + The new user will not be a superuser. + This is the default. diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml index 76324df160..3644eb97fa 100644 --- a/doc/src/sgml/ref/vacuumdb.sgml +++ b/doc/src/sgml/ref/vacuumdb.sgml @@ -1,5 +1,5 @@ @@ -127,16 +127,6 @@ PostgreSQL documentation - - - - - - Only calculate statistics for use by the optimizer (no vacuum). - - - - @@ -195,6 +185,16 @@ PostgreSQL documentation + + + + + + Only calculate statistics for use by the optimizer (no vacuum). + + + +