The catalog pg_default_acl stores initial privileges to be assigned to newly created objects.
Table 47-17. pg_default_acl Columns
|oid||oid||Row identifier (hidden attribute; must be explicitly selected)|
|defaclrole||oid||pg_authid.oid||The OID of the role associated with this entry|
|defaclnamespace||oid||pg_namespace.oid||The OID of the namespace associated with this entry, or 0 if none|
|defaclobjtype||char||Type of object this entry is for: r = relation (table, view), S = sequence, f = function, T = type|
|defaclacl||aclitem||Access privileges that this type of object should have on creation|
A pg_default_acl entry shows the initial privileges to be assigned to an object belonging to the indicated user. There are currently two types of entry: "global" entries with defaclnamespace = 0, and "per-schema" entries that reference a particular schema. If a global entry is present then it overrides the normal hard-wired default privileges for the object type. A per-schema entry, if present, represents privileges to be added to the global or hard-wired default privileges.
Note that when an ACL entry in another catalog is null, it is taken to represent the hard-wired default privileges for its object, not whatever might be in pg_default_acl at the moment. pg_default_acl is only consulted during object creation.
Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.
Proceed to the comment form.