PG_USER
PG_USER displays information about database users. By default, only the initial user and users with the sysadmin attribute can view the information. Other users can view the information only after being granted with permissions.
Name |
Type |
Description |
---|---|---|
usename |
name |
Username. |
usesysid |
oid |
ID of this user. |
usecreatedb |
Boolean |
Specifies whether a user has the permissions to create databases.
|
usesuper |
Boolean |
Specifies whether the user is the initial system administrator with the highest permissions.
|
usecatupd |
Boolean |
Specifies whether the user can directly update system catalogs. Only the initial system administrator whose usesysid is 10 has this permission. This permission is unavailable for other users.
|
userepl |
Boolean |
Specifies whether the user has the permissions to duplicate data streams.
|
passwd |
text |
Encrypted user password. The value is displayed as ********. |
valbegin |
timestamp with time zone |
Start time for account validity (NULL if the start time is not specified). |
valuntil |
timestamp with time zone |
End time for account validity (NULL if the end time is not specified). |
respool |
name |
Resource pool where the user is in. |
parent |
oid |
Parent user OID. |
spacelimit |
text |
Storage space of the permanent table, in KB. |
useconfig |
text[] |
Default value of runtime configuration items. For details, see setconfig in PG_DB_ROLE_SETTING. |
nodegroup |
name |
Name of the logical database associated with the user. If the user does not manage the logical database, this column is left blank. |
tempspacelimit |
text |
Storage space of the temporary table, in KB. |
spillspacelimit |
text |
Operator disk spill space, in KB. |
usemonitoradmin |
Boolean |
Specifies whether the user is a monitor administrator.
|
useoperatoradmin |
Boolean |
Specifies whether the user is an O&M administrator.
|
usepolicyadmin |
Boolean |
Specifies whether the user is a security policy administrator.
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot