Movatterモバイル変換

ALTER DEFAULT PRIVILEGES

ALTER DEFAULT PRIVILEGES — define default access privileges

Synopsis

ALTER DEFAULT PRIVILEGES    [ FOR { ROLE | USER }target_role [, ...] ]    [ IN SCHEMAschema_name [, ...] ]abbreviated_grant_or_revokewhereabbreviated_grant_or_revoke is one of:GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER | MAINTAIN }    [, ...] | ALL [ PRIVILEGES ] }    ON TABLES    TO { [ GROUP ]role_name | PUBLIC } [, ...] [ WITH GRANT OPTION ]GRANT { { USAGE | SELECT | UPDATE }    [, ...] | ALL [ PRIVILEGES ] }    ON SEQUENCES    TO { [ GROUP ]role_name | PUBLIC } [, ...] [ WITH GRANT OPTION ]GRANT { EXECUTE | ALL [ PRIVILEGES ] }    ON { FUNCTIONS | ROUTINES }    TO { [ GROUP ]role_name | PUBLIC } [, ...] [ WITH GRANT OPTION ]GRANT { USAGE | ALL [ PRIVILEGES ] }    ON TYPES    TO { [ GROUP ]role_name | PUBLIC } [, ...] [ WITH GRANT OPTION ]GRANT { { USAGE | CREATE }    [, ...] | ALL [ PRIVILEGES ] }    ON SCHEMAS    TO { [ GROUP ]role_name | PUBLIC } [, ...] [ WITH GRANT OPTION ]REVOKE [ GRANT OPTION FOR ]    { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | TRIGGER | MAINTAIN }    [, ...] | ALL [ PRIVILEGES ] }    ON TABLES    FROM { [ GROUP ]role_name | PUBLIC } [, ...]    [ CASCADE | RESTRICT ]REVOKE [ GRANT OPTION FOR ]    { { USAGE | SELECT | UPDATE }    [, ...] | ALL [ PRIVILEGES ] }    ON SEQUENCES    FROM { [ GROUP ]role_name | PUBLIC } [, ...]    [ CASCADE | RESTRICT ]REVOKE [ GRANT OPTION FOR ]    { EXECUTE | ALL [ PRIVILEGES ] }    ON { FUNCTIONS | ROUTINES }    FROM { [ GROUP ]role_name | PUBLIC } [, ...]    [ CASCADE | RESTRICT ]REVOKE [ GRANT OPTION FOR ]    { USAGE | ALL [ PRIVILEGES ] }    ON TYPES    FROM { [ GROUP ]role_name | PUBLIC } [, ...]    [ CASCADE | RESTRICT ]REVOKE [ GRANT OPTION FOR ]    { { USAGE | CREATE }    [, ...] | ALL [ PRIVILEGES ] }    ON SCHEMAS    FROM { [ GROUP ]role_name | PUBLIC } [, ...]    [ CASCADE | RESTRICT ]

Description#

ALTER DEFAULT PRIVILEGES allows you to set the privileges that will be applied to objects created in the future. (It does not affect privileges assigned to already-existing objects.) Privileges can be set globally (i.e., for all objects created in the current database), or just for objects created in specified schemas.

While you can change your own default privileges and the defaults of roles that you are a member of, at object creation time, new object permissions are only affected by the default privileges of the current role, and are not inherited from any roles in which the current role is a member.

As explained inSection 5.8, the default privileges for any object type normally grant all grantable permissions to the object owner, and may grant some privileges toPUBLIC as well. However, this behavior can be changed by altering the global default privileges withALTER DEFAULT PRIVILEGES.

Currently, only the privileges for schemas, tables (including views and foreign tables), sequences, functions, and types (including domains) can be altered. For this command, functions include aggregates and procedures. The wordsFUNCTIONS andROUTINES are equivalent in this command. (ROUTINES is preferred going forward as the standard term for functions and procedures taken together. In earlier Postgres Pro releases, only the wordFUNCTIONS was allowed. It is not possible to set default privileges for functions and procedures separately.)

Default privileges that are specified per-schema are added to whatever the global default privileges are for the particular object type. This means you cannot revoke privileges per-schema if they are granted globally (either by default, or according to a previousALTER DEFAULT PRIVILEGES command that did not specify a schema). Per-schemaREVOKE is only useful to reverse the effects of a previous per-schemaGRANT.

Notes#

Usepsql's\ddp command to obtain information about existing assignments of default privileges. The meaning of the privilege display is the same as explained for\dp inSection 5.8.

If you wish to drop a role for which the default privileges have been altered, it is necessary to reverse the changes in its default privileges or useDROP OWNED BY to get rid of the default privileges entry for the role.

Examples#

Grant SELECT privilege to everyone for all tables (and views) you subsequently create in schemamyschema, and allow rolewebuser to INSERT into them too:

ALTER DEFAULT PRIVILEGES IN SCHEMA myschema GRANT SELECT ON TABLES TO PUBLIC;ALTER DEFAULT PRIVILEGES IN SCHEMA myschema GRANT INSERT ON TABLES TO webuser;

Undo the above, so that subsequently-created tables won't have any more permissions than normal:

ALTER DEFAULT PRIVILEGES IN SCHEMA myschema REVOKE SELECT ON TABLES FROM PUBLIC;ALTER DEFAULT PRIVILEGES IN SCHEMA myschema REVOKE INSERT ON TABLES FROM webuser;

Remove the public EXECUTE permission that is normally granted on functions, for all functions subsequently created by roleadmin:

ALTER DEFAULT PRIVILEGES FOR ROLE admin REVOKE EXECUTE ON FUNCTIONS FROM PUBLIC;

Note however that youcannot accomplish that effect with a command limited to a single schema. This command has no effect, unless it is undoing a matchingGRANT:

ALTER DEFAULT PRIVILEGES IN SCHEMA public REVOKE EXECUTE ON FUNCTIONS FROM PUBLIC;

That's because per-schema default privileges can only add privileges to the global setting, not remove privileges granted by it.

Compatibility

There is noALTER DEFAULT PRIVILEGES statement in the SQL standard.

See Also