(Note that there is no option to add the new role as an administrator use a separate GRANT command to do that.) IN GROUP role_name The IN ROLE clause lists one or more existing roles to which the new role will be immediately added as a new member.
#POSTGRES CREATE SUPERUSER PASSWORD#
If this clause is omitted the password will be valid for all time. The VALID UNTIL clause sets a date and time after which the role's password is no longer valid. This allows reloading of encrypted passwords during dump/restore. If the presented password string is already in MD5-encrypted or SCRAM-encrypted format, then it is stored as-is regardless of password_encryption (since the system cannot decrypt the specified encrypted password string, to encrypt it in a different format).
The method of encryption is determined by the configuration parameter password_encryption. The ENCRYPTED keyword has no effect, but is accepted for backwards compatibility. The password is always stored encrypted in the system catalogs. To avoid the ambiguity, specifying an empty string should be avoided. In earlier versions, an empty string could be used, or not, depending on the authentication method and the exact version, and libpq would refuse to use it in any case. Specifying an empty string will also set the password to null, but that was not the case before PostgreSQL version 10. A null password can optionally be written explicitly as PASSWORD NULL. If no password is specified, the password will be set to null and password authentication will always fail for that user. (A password is only of use for roles having the LOGIN attribute, but you can nonetheless define one for roles without it.) If you do not plan to use password authentication you can omit this option. Neither prepared transactions nor background worker connections are counted towards this limit. Note that only normal connections are counted towards this limit. If role can log in, this specifies how many concurrent connections the role can make. However, superusers and the owner of the table being dumped always bypass RLS. If the user running pg_dump does not have appropriate permissions, an error will be returned. Note that pg_dump will set row_security to OFF by default, to ensure all contents of a table are dumped out. You must be a superuser to create a new role having the BYPASSRLS attribute.
These clauses determine whether a role bypasses every row-level security (RLS) policy. You must be a superuser to create a new role having the REPLICATION attribute. If not specified, NOREPLICATION is the default. A role having the REPLICATION attribute is a very highly privileged role, and should only be used on roles actually used for replication. A role must have this attribute (or be a superuser) in order to be able to connect to the server in replication mode (physical or logical replication) and in order to be able to create or drop replication slots. These clauses determine whether a role is a replication role. If not specified, NOLOGIN is the default, except when CREATE ROLE is invoked through its alternative spelling CREATE USER. Roles without this attribute are useful for managing database privileges, but are not users in the usual sense of the word. A role having the LOGIN attribute can be thought of as a user. These clauses determine whether a role is allowed to log in that is, whether the role can be given as the initial session authorization name during client connection. If not specified, INHERIT is the default. Without INHERIT, membership in another role only grants the ability to SET ROLE to that other role the privileges of the other role are only available after having done so. A role with the INHERIT attribute can automatically use whatever database privileges have been granted to all roles it is directly or indirectly a member of. These clauses determine whether a role “ inherits” the privileges of roles it is a member of. If not specified, NOCREATEROLE is the default. See role creation for more details about what capabilities are conferred by this privilege. These clauses determine whether a role will be permitted to create, alter, drop, comment on, change the security label for, and grant or revoke membership in other roles. If not specified, NOCREATEDB is the default. Specifying NOCREATEDB will deny a role the ability to create databases. If CREATEDB is specified, the role being defined will be allowed to create new databases. These clauses define a role's ability to create databases. If not specified, NOSUPERUSER is the default. You must yourself be a superuser to create a new superuser. Superuser status is dangerous and should be used only when really needed. These clauses determine whether the new role is a “ superuser”, who can override all access restrictions within the database.
0 kommentar(er)
