PostgreSQL

  +
  (`+CREATE USER+` is equivalent to `+CREATE ROLE+` except that `+CREATE USER+` includes `+LOGIN+` by default, while `+CREATE ROLE+` does not.)
[.term]#superuser status::
  A database superuser bypasses all permission checks, except the right to log in. This is a dangerous privilege and should not be used carelessly; it is best to do most of your work as a role that is not a superuser. To create a new database superuser, use `+CREATE ROLE +`_`+name+`_`+ SUPERUSER+`. You must do this as a role that is already a superuser.
[.term]#database creation::
  A role must be explicitly given permission to create databases (except for superusers, since those bypass all permission checks). To create such a role, use `+CREATE ROLE +`_`+name+`_`+ CREATEDB+`.
[#ROLE-CREATION .term]#role creation::
  A role must be explicitly given permission to create more roles (except for superusers, since those bypass all permission checks). To create such a role, use `+CREATE ROLE +`_`+name+`_`+ CREATEROLE+`. A role with `+CREATEROLE+` privilege can alter and drop roles which have been granted to the `+CREATEROLE+` user with the `+ADMIN+` option. Such a grant occurs automatically when a `+CREATEROLE+` user that is not a superuser creates a new role, so that by default, a `+CREATEROLE+` user can alter and drop the roles which they have created. Altering a role includes most changes that can be made using `+ALTER ROLE+`, including, for example, changing passwords. It also includes modifications to a role that can be made using the `+COMMENT+` and `+SECURITY LABEL+` commands.
  +
  However, `+CREATEROLE+` does not convey the ability to create `+SUPERUSER+` roles, nor does it convey any power over `+SUPERUSER+` roles that already exist. Furthermore, `+CREATEROLE+` does not convey the power to create `+REPLICATION+` users, nor the ability to grant or revoke the `+REPLICATION+` privilege, nor the ability to modify the role properties of such users. However, it does allow `+ALTER ROLE ... SET+` and `+ALTER ROLE ... RENAME+` to be used on `+REPLICATION+` roles, as well as the use of `+COMMENT ON ROLE+`, `+SECURITY LABEL ON ROLE+`, and `+DROP ROLE+`. Finally, `+CREATEROLE+` does not confer the ability to grant or revoke the `+BYPASSRLS+` privilege.
[.term]#initiating replication::
  A role must explicitly be given permission to initiate streaming replication (except for superusers, since those bypass all permission checks). A role used for streaming replication must have `+LOGIN+` permission as well. To create such a role, use `+CREATE ROLE +`_`+name+`_`+ REPLICATION LOGIN+`.
[.term]#password::
  A password is only significant if the client authentication method requires the user to supply a password when connecting to the database. The `+password+` and `+md5+` authentication methods make use of passwords. Database passwords are separate from operating system passwords. Specify a password upon role creation with `+CREATE ROLE +`_`+name+`_`+ PASSWORD '+`_`+string+`_`+'+`.
[.term]#inheritance of privileges::
  A role inherits the privileges of roles it is a member of, by default. However, to create a role which does not inherit privileges by default, use `+CREATE ROLE +`_`+name+`_`+ NOINHERIT+`. Alternatively, inheritance can be overridden for individual grants by using `+WITH INHERIT TRUE+` or `+WITH INHERIT FALSE+`.
[.term]#bypassing row-level security::
  A role must be explicitly given permission to bypass every row-level security (RLS) policy (except for superusers, since those bypass all permission checks). To create such a role, use `+CREATE ROLE +`_`+name+`_`+ BYPASSRLS+` as a superuser.
[.term]#connection limit::
  Connection limit can specify how many concurrent connections a role can make. -1 (the default) means no limit. Specify connection limit upon role creation with `+CREATE ROLE +`_`+name+`_`+ CONNECTION LIMIT '+`_`+integer+`_`+'+`.