Skip to content

Altering attributes

Attributes are PostgreSQL’s role flags. Unlike other settings, the list of flags is fixed; there is no option to add or remove any.

Attributes section

Attributes section

Attributes section

It supports following attributes:

AttributeKeyword
SuperuserSUPERUSER / NOSUPERUSER
Create roleCREATEROLE / NOCREATEROLE
Create DBCREATEDB / NOCREATEDB
InheritINHERIT / NOINHERIT
LoginLOGIN / NOLOGIN
ReplicationREPLICATION / NOREPLICATION
Bypass RLSBYPASSRLS / NOBYPASSRLS

All seven rows always render, depicting clusters where are enabled. If the particular attribute is enabled nowhere, the off symbol is displayed.

ButtonEffect
EditPer-cluster editor — tick to enable, untick to disable.
RemoveDisables the attribute on every cluster in scope.
DiscardDiscards pending changes on that row.

Click on Edit button opens the popup with selection of clusters

Per-cluster attribute editor

Per-cluster attribute editor

Per-cluster attribute editor

Pending changes are visible before you save, through the shared scope-label convention: a pending grant is prefixed with +, a pending revoke turns red and struck through.

When executing all of a cluster’s attribute changes are combined into a single ALTER ROLE … WITH keyword keyword … query, so enabling LOGIN and disabling SUPERUSER turns into single statement, not two.