to do that.
-
- CREATE USER
-
+ CREATE USER
SQL - Language Statements
+
-
- CREATE USER
-
-
- define a new database user account
-
+ CREATE USER
+ define a new database user account
+
-
- 2001-07-10
-
-
+
CREATE USER username [ [ WITH ] option [ ... ] ]
where option can be:
- SYSID uid
- | [ ENCRYPTED | UNENCRYPTED ] PASSWORD 'password'
- | CREATEDB | NOCREATEDB
- | CREATEUSER | NOCREATEUSER
- | IN GROUP groupname [, ...]
- | VALID UNTIL 'abstime'
-
-
-
-
- 1998-09-21
-
-
- Inputs
-
+ SYSID uid
+ | [ ENCRYPTED | UNENCRYPTED ] PASSWORD 'password'
+ | CREATEDB | NOCREATEDB
+ | CREATEUSER | NOCREATEUSER
+ | IN GROUP groupname [, ...]
+ | VALID UNTIL 'abstime'
+
+
+
+
+
Description
+
+ CREATE USER will add a new user to an instance
+ of
PostgreSQL. Refer to the
+ Administrator's Guide for information about
+ managing users and authentication. You must be a database
+ superuser to use this command.
+
+
+
+
Parameters
+
uid
- The SYSID clause can be used to choose
- the
PostgreSQL user id of the user
- that is being created. It is not at all necessary that those
- match the
UNIX user ids, but some people
- choose to keep the numbers the same.
+ The SYSID clause can be used to choose the
+
PostgreSQL user ID of the user that
+ is being created. It is not at all necessary that those match
+ the Unix user IDs, but some people choose to keep the numbers
+ the same.
- If this is not specified, the highest assigned user id plus one
+ If this is not specified, the highest assigned user ID plus one
(with a minimum of 100) will be used as default.
- ENCRYPTED
- UNENCRYPTED
+ ENCRYPTED>
+ UNENCRYPTED>
- These keywords control whether the
- password is stored encrypted in pg_shadow>. (If neither
- is specified, the default behavior is determined by the
- PASSWORD_ENCRYPTION server parameter.)
- If the presented string is already in MD5-encrypted format,
- then it is stored as-is, regardless of whether
- ENCRYPTED or UNENCRYPTED
- is specified. This allows reloading of encrypted passwords
- during dump/restore.
-
+ These keywords control whether the password is stored
+ encrypted in pg_shadow>. (If neither is specified,
+ the default behavior is determined by the
+ PASSWORD_ENCRYPTION server parameter.) If
+ the presented string is already in MD5-encrypted format, then
+ it is stored as-is, regardless of whether
+ ENCRYPTED> or UNENCRYPTED> is specified.
+ This allows reloading of encrypted passwords during
+ dump/restore.
+
+
See the chapter on client authentication in the
- Administrator's Guide for details on
- how to set up authentication mechanisms. Note that older clients
- may lack support for the MD5 authentication mechanism that's needed
- to work with passwords that are stored encrypted.
+ Administrator's Guide for details on
+ how to set up authentication mechanisms. Note that older
+ clients may lack support for the MD5 authentication mechanism
+ that is needed to work with passwords that are stored
+ encrypted.
- CREATEDB
- NOCREATEDB
+ CREATEDB>
+ NOCREATEDB>
- These clauses define a user's ability to create databases.
- If CREATEDB is specified, the user being defined will
- be allowed to create his own databases. Using NOCREATEDB
- will deny a user the ability to create databases. If this
- clause is omitted, NOCREATEDB is used by default.
+ These clauses define a user's ability to create databases. If
+ CREATEDB is specified, the user being
+ defined will be allowed to create his own databases. Using
+ NOCREATEDB will deny a user the ability to
+ create databases. If this clause is omitted,
+ NOCREATEDB is used by default.
- CREATEUSER
- NOCREATEUSER
+ CREATEUSER
+ NOCREATEUSER
These clauses determine whether a user will be permitted to
create new users himself. This option will also make the user
- a superuser who can override all access restrictions.
+ a superuser who can override all access restrictions.
Omitting this clause will set the user's value of this
- attribute to be NOCREATEUSER.
+ attribute to be NOCREATEUSER.
abstime
- The VALID UNTIL clause sets an absolute time after which the
- user's password is no longer valid.
- If this clause is omitted the login will be valid for all time.
+ The VALID UNTIL clause sets an absolute
+ time after which the user's password is no longer valid. If
+ this clause is omitted the login will be valid for all time.
-
-
-
- 1998-09-21
-
-
- Outputs
-
-
-
- CREATE USER
-
- Message returned if the command completes successfully.
-
-
-
-
-
-
-
+
+
+
+
Diagnostics
-
-
- 1998-09-21
-
-
- Description
-
- CREATE USER will add a new user to an instance of
-
PostgreSQL. Refer to the administrator's
- guide for information about managing users and authentication.
- You must be a database superuser to use this command.
+
+
+ CREATE USER
+
+ Message returned if the command completes successfully.
+
+
+
+
+
+
+
+
Notes
+
- Use
- to change a user's password and privileges, and
- endterm="SQL-DROPUSER-title"> to remove a user.
- Use
- to add or remove the user from other groups.
- comes with a script
- endterm="APP-CREATEUSER-title">
- which has the same functionality as this command (in fact, it calls this command)
- but can be run from the command shell.
-
-
-
-
- Usage
-
+ Use to
+ change the attributes of a user, and
+ endterm="SQL-DROPUSER-title"> to remove a user. Use
+ linkend="SQL-ALTERGROUP" endterm="SQL-ALTERGROUP-title"> to add the
+ user to groups or remove the user from groups.
+
PostgreSQL includes a program
+ linkend="APP-CREATEUSER" endterm="APP-CREATEUSER-title"> that has
+ the same functionality as this command (in fact, it calls this
+ command) but can be run from the command shell.
+
+
+
+
+
Examples
+
Create a user with no password:
-CREATE USER jonathan
+CREATE USER jonathan;
-
-
- Compatibility
-
+
+
Compatibility
-
-
- 1998-09-21
-
-
- SQL92
-
+ The CREATE USER statement is a
+
PostgreSQL extension. The SQL standard
+ leaves the definition of users to the implementation.
+
+
- There is no CREATE USER statement in SQL92.
-
-
+
+
See Also
+
+
+
+
+
+
-
- DROP USER
-
+ DROP USER
SQL - Language Statements
-
- DROP USER
-
-
- remove a database user account
-
+ DROP USER
+ remove a database user account
+
-
- 1999-07-20
-
-
+
DROP USER name
-
-
-
-
- 1998-09-22
-
-
- Inputs
-
+
+
+
+
Description
+
+ DROP USER removes the specified user from the database.
+ It does not remove tables, views, or other objects owned by the user. If the
+ user owns any database, an error is raised.
+
+
+
+
Parameters
+
name
-
-
-
- 1998-09-22
-
-
- Outputs
-
-
-
- DROP USER
-
- The message returned if the user is successfully deleted.
-
-
-
-
-
-
-ERROR: DROP USER: user "name" does not exist
-
-
- This message occurs if the user name is not found.
-
-
-
-
-
-DROP USER: user "name" owns database "name", cannot be removed
-
-
- You must drop the database first or change its ownership.
-
-
-
+
-
-
-
-
+
+
Diagnostics
-
-
- 1998-09-22
-
-
- Description
-
- DROP USER removes the specified user from the database.
- It does not remove tables, views, or other objects owned by the user. If the
- user owns any database you get an error.
+
+
+ DROP USER
+
+ The message returned if the user is successfully deleted.
+
+
+
+
+
+ ERROR: DROP USER: user "name" does not exist
+
+ This message occurs if the user name is not found.
+
+
+
+
+
+ DROP USER: user "name" owns database "name", cannot be removed
+
+ You must drop the database first or change its ownership.
+
+
+
+
+
+
+
+
+
Notes
+
Use
to add new users, and
- endterm="SQL-ALTERUSER-title"> to change a user's properties.
- comes with a script
- endterm="APP-DROPUSER-title">
- which has the same functionality as this command (in fact, it calls this command)
+ endterm="SQL-ALTERUSER-title"> to change a user's attributes.
+
PostgreSQL includes a program
+ linkend="APP-DROPUSER" endterm="APP-DROPUSER-title"> that has the
+ same functionality as this command (in fact, it calls this command)
but can be run from the command shell.
-
+
-
-
- Usage
-
+
+
Examples
+
To drop a user account:
-
-
- Compatibility
-
+
+
Compatibility
-
-
- 1998-09-22
-
-
- SQL92
-
- There is no
DROP USER in
SQL92.
-
-
+ The DROP USER statement is a
+
PostgreSQL extension. The SQL standard
+ leaves the definition of users to the implementation.
+
+
+
+
See Also
+
+
+
+
+
+
+
+