18.3. privileges

when an object is created, it is assigned an owner. the owner is normally the role that executed the creation statement. for most kinds of objects, the initial state is that only the owner (or a superuser) can do anything with the object. to allow other roles to use it, privileges must be granted. there are several different kinds of privilege: select, insert, update, delete, rule, references, trigger, create, temporary, execute, and usage. for more information on the different types of privileges supported by postgresql, see the grant reference page.

to assign privileges, the grant command is used. so, if joe is an existing role, and accounts is an existing table, the privilege to update the table can be granted with

grant update on accounts to joe;

the special name public can be used to grant a privilege to every role on the system. writing all in place of a specific privilege specifies that all privileges that apply to the object will be granted.

to revoke a privilege, use the fittingly named revoke command:

revoke all on accounts from public;

the special privileges of an object's owner (i.e., the right to modify or destroy the object) are always implicit in being the owner, and cannot be granted or revoked. but the owner can choose to revoke his own ordinary privileges, for example to make a table read-only for himself as well as others.

an object can be assigned to a new owner with an alter command of the appropriate kind for the object. superusers can always do this; ordinary roles can only do it if they are both the current owner of the object (or a member of the owning role) and a member of the new owning role.