GRANT — 賦予存取權限
GRANT 指令有兩個基本用法：一個是授予資料庫物件（資料表、欄位、檢視表、外部資料表、序列、資料庫、外部資料封裝、外部伺服器、函數、程序語言、綱要或資料表空間）的權限；另一個則是授予角色成員資格的人。這些用法在許多方面類似，但它們的不同之處將會單獨描述。
在資料庫物件上的 GRANT
GRANT 指令的這個用法為資料庫物件提供了對一個或多個角色的特定權限。這些權限將會附加到已授予的權限（如果有的話）。
還有一個選項可以在一個或多個綱要中為相同類型的所有物件授予權限。目前僅有資料、序列和函數支援此功能（但請注意，ALL TABLES 被視為包括檢視圖和外部資料表）。
關鍵字 PUBLIC 表示將權限授予所有角色，包括稍後可能建立的角色。 PUBLIC 可以被視為一個隱性定義的群組，它包含了所有角色。任何特定角色都將擁有直接授予它的權限總和，也就是授予其目前成員的任何角色的權限，加上授予 PUBLIC 的權限。
如果指定了 WITH GRANT OPTION，則權限的被授予者可以將該權限授予其他人。如果沒有授權選項，被授予者就無法執行此操作。授權選項不能授予 PUBLIC。
毌須向物件的所有者（通常是建立它的使用者）授予權限，因為預設情況下所有者具備所有權限。 （但是，所有者可以選擇撤銷他們自己的一些安全權限。）
刪除物件或以任何方式變更其定義的權利將不被視為可授予的權限；它是所有者固有的，不能被授予或撤銷。（但是，透過授予或撤銷擁有該物件的角色成員資格可以獲得類似的效果；請參閱下文。）所有者也隱含地擁有該物件的所有授權選項。
PostgreSQL 將某些類型物件的預設權限授予 PUBLIC。預設情況下，對資料表、資料表欄位、序列、外部資料封裝、外部伺服器、大型物件、綱要或資料表空間不會授予 PUBLIC 權限。對於其他類型的物件，授予 PUBLIC 的預設權限如下：CONNECT 和 TEMPORARY（建立臨時資料表）資料庫權限；函數的 EXECUTE 權限；以及語言和資料型別（包括 domain）的 USAGE 權限。當然，物件所有者可以撤銷預設和明確授予的權限。（為了最大限度地提高安全性，請在建立物件的同一交易事務中發出 REVOKE；如此就沒有其他用戶可以使用該物件的窗口。）此外，可以使用 ALTER DEFAULT PRIVILEGES 指令更改這些初始預設權限設定。
The possible privileges are:
SELECT
Allows SELECT from any column, or the specific columns listed, of the specified table, view, or sequence. Also allows the use of COPY TO. This privilege is also needed to reference existing column values in UPDATE or DELETE. For sequences, this privilege also allows the use of the currval function. For large objects, this privilege allows the object to be read.
INSERT
Allows INSERT of a new row into the specified table. If specific columns are listed, only those columns may be assigned to in the INSERT command (other columns will therefore receive default values). Also allows COPY FROM.
UPDATE
Allows UPDATE of any column, or the specific columns listed, of the specified table. (In practice, any nontrivial UPDATE command will require SELECT privilege as well, since it must reference table columns to determine which rows to update, and/or to compute new values for columns.) SELECT ... FOR UPDATE and SELECT ... FOR SHARE also require this privilege on at least one column, in addition to the SELECT privilege. For sequences, this privilege allows the use of the nextval and setval functions. For large objects, this privilege allows writing or truncating the object.
DELETE
Allows DELETE of a row from the specified table. (In practice, any nontrivial DELETE command will require SELECT privilege as well, since it must reference table columns to determine which rows to delete.)
TRUNCATE
Allows TRUNCATE on the specified table.
REFERENCES
Allows creation of a foreign key constraint referencing the specified table, or specified column(s) of the table. (See the CREATE TABLE statement.)
TRIGGER
Allows the creation of a trigger on the specified table. (See the CREATE TRIGGER statement.)
CREATE
For databases, allows new schemas and publications to be created within the database.
For schemas, allows new objects to be created within the schema. To rename an existing object, you must own the object and have this privilege for the containing schema.
For tablespaces, allows tables, indexes, and temporary files to be created within the tablespace, and allows databases to be created that have the tablespace as their default tablespace. (Note that revoking this privilege will not alter the placement of existing objects.)
CONNECT
Allows the user to connect to the specified database. This privilege is checked at connection startup (in addition to checking any restrictions imposed by pg_hba.conf).
TEMPORARY
TEMP
Allows temporary tables to be created while using the specified database.
EXECUTE
Allows the use of the specified function and the use of any operators that are implemented on top of the function. This is the only type of privilege that is applicable to functions. (This syntax works for aggregate functions, as well.)
USAGE
For procedural languages, allows the use of the specified language for the creation of functions in that language. This is the only type of privilege that is applicable to procedural languages.
For schemas, allows access to objects contained in the specified schema (assuming that the objects' own privilege requirements are also met). Essentially this allows the grantee to “look up” objects within the schema. Without this permission, it is still possible to see the object names, e.g. by querying the system tables. Also, after revoking this permission, existing backends might have statements that have previously performed this lookup, so this is not a completely secure way to prevent object access.
For sequences, this privilege allows the use of the currval and nextval functions.
For types and domains, this privilege allows the use of the type or domain in the creation of tables, functions, and other schema objects. (Note that it does not control general “usage” of the type, such as values of the type appearing in queries. It only prevents objects from being created that depend on the type. The main purpose of the privilege is controlling which users create dependencies on a type, which could prevent the owner from changing the type later.)
For foreign-data wrappers, this privilege allows creation of new servers using the foreign-data wrapper.
For servers, this privilege allows creation of foreign tables using the server. Grantees may also create, alter, or drop their own user mappings associated with that server.
ALL PRIVILEGES
Grant all of the available privileges at once. The PRIVILEGES key word is optional in PostgreSQL, though it is required by strict SQL.
The privileges required by other commands are listed on the reference page of the respective command.
This variant of the GRANT command grants membership in a role to one or more other roles. Membership in a role is significant because it conveys the privileges granted to a role to each of its members.
If WITH ADMIN OPTION is specified, the member can in turn grant membership in the role to others, and revoke membership in the role as well. Without the admin option, ordinary users cannot do that. A role is not considered to hold WITH ADMIN OPTION on itself, but it may grant or revoke membership in itself from a database session where the session user matches the role. Database superusers can grant or revoke membership in any role to anyone. Roles having CREATEROLE privilege can grant or revoke membership in any role that is not a superuser.
Unlike the case with privileges, membership in a role cannot be granted to PUBLIC. Note also that this form of the command does not allow the noise word GROUP.
The REVOKE command is used to revoke access privileges.
Since PostgreSQL 8.1, the concepts of users and groups have been unified into a single kind of entity called a role. It is therefore no longer necessary to use the keyword GROUP to identify whether a grantee is a user or a group. GROUP is still allowed in the command, but it is a noise word.
A user may perform SELECT, INSERT, etc. on a column if they hold that privilege for either the specific column or its whole table. Granting the privilege at the table level and then revoking it for one column will not do what one might wish: the table-level grant is unaffected by a column-level operation.
When a non-owner of an object attempts to GRANT privileges on the object, the command will fail outright if the user has no privileges whatsoever on the object. As long as some privilege is available, the command will proceed, but it will grant only those privileges for which the user has grant options. The GRANT ALL PRIVILEGES forms will issue a warning message if no grant options are held, while the other forms will issue a warning if grant options for any of the privileges specifically named in the command are not held. (In principle these statements apply to the object owner as well, but since the owner is always treated as holding all grant options, the cases can never occur.)
It should be noted that database superusers can access all objects regardless of object privilege settings. This is comparable to the rights of root in a Unix system. As with root, it's unwise to operate as a superuser except when absolutely necessary.
If a superuser chooses to issue a GRANT or REVOKE command, the command is performed as though it were issued by the owner of the affected object. In particular, privileges granted via such a command will appear to have been granted by the object owner. (For role membership, the membership appears to have been granted by the containing role itself.)
GRANT and REVOKE can also be done by a role that is not the owner of the affected object, but is a member of the role that owns the object, or is a member of a role that holds privilegesWITH GRANT OPTION on the object. In this case the privileges will be recorded as having been granted by the role that actually owns the object or holds the privileges WITH GRANT OPTION. For example, if table t1 is owned by role g1, of which role u1 is a member, then u1 can grant privileges on t1 to u2, but those privileges will appear to have been granted directly by g1. Any other member of role g1 could revoke them later.
If the role executing GRANT holds the required privileges indirectly via more than one role membership path, it is unspecified which containing role will be recorded as having done the grant. In such cases it is best practice to use SET ROLE to become the specific role you want to do the GRANT as.
Granting permission on a table does not automatically extend permissions to any sequences used by the table, including sequences tied to SERIAL columns. Permissions on sequences must be set separately.
Use psql's \dp command to obtain information about existing privileges for tables and columns. For example:
The entries shown by \dp are interpreted thus:
The above example display would be seen by user miriam after creating table mytable and doing:
For non-table objects there are other \d commands that can display their privileges.
If the “Access privileges” column is empty for a given object, it means the object has default privileges (that is, its privileges column is null). Default privileges always include all privileges for the owner, and can include some privileges for PUBLIC depending on the object type, as explained above. The first GRANT or REVOKE on an object will instantiate the default privileges (producing, for example, {miriam=arwdDxt/miriam}) and then modify them per the specified request. Similarly, entries are shown in “Column access privileges” only for columns with nondefault privileges. (Note: for this purpose, “default privileges” always means the built-in default privileges for the object's type. An object whose privileges have been affected by an ALTER DEFAULT PRIVILEGES command will always be shown with an explicit privilege entry that includes the effects of the ALTER.)
Notice that the owner's implicit grant options are not marked in the access privileges display. A * will appear only when grant options have been explicitly granted to someone.
把向資料表 film 插入資料的權限授予所有使用者：
把所有檢視表 kind 可用的權限授予使用者 manuel：
請注意，雖然如果由超級使用者或該型別的擁有者執行，上述內容確實會授予所有權限；但當由其他人執行時，它將僅授予其他人其所擁有授權選項的權限。
將角色 admin 的成員資格授予使用者 joe：
根據 SQL 標準，ALL PRIVILEGES 中的 PRIVILEGES 關鍵字是需要的。SQL 標準不支援在指令設定多個物件的權限。
PostgreSQL 允許物件擁有者撤銷他們自己的普通權限：例如，資料表擁有者可以透過撤銷自己的 INSERT，UPDATE，DELETE 和 TRUNCATE 權限使資料表對自己而言是唯讀。但根據 SQL 標準，這是不可能的。原因是 PostgreSQL 將擁有者的權限視為已由擁有者授予他們自己；因此他們自己也可以撤銷它們。在 SQL 標準中，擁有者的權限由假設上的實體「_SYSTEM」授予。由於不是「_SYSTEM」，擁有者就不能撤銷這些權利。
根據 SQL 標準，可以向 PUBLIC 授予授權選項；PostgreSQL 僅支援向角色授予授權選項。
SQL 標準為其他型別的物件提供 USAGE 權限：字元集，排序規則，翻譯。
在 SQL 標準中，序列只有 USAGE 權限，它控制 NEXT VALUE FOR 表示式的使用，這相當於 PostgreSQL 中的 nextval 函數。序列權限 SELECT 和 UPDATE 是 PostgreSQL 的延伸功能。將序列 USAGE 權限套用於 currval 函數也是 PostgreSQL 的延伸功能（函數本身也是如此）。
資料庫，資料表空間，綱要和語言的權限都是 PostgreSQL 的延伸功能。