PG_SHDEPEND
PG_SHDEPEND records the dependency between database objects and shared objects, such as roles. Based on this information, GaussDB can ensure that those objects are unreferenced before attempting to delete them.
See also PG_DEPEND, which provides a similar function for dependencies involving objects within a single database.
PG_SHDEPEND is shared among all databases of a database instance. That is, there is only one PG_SHDEPEND for each instance, not for each database.
Name |
Type |
Reference |
Description |
---|---|---|---|
dbid |
oid |
oid in PG_DATABASE |
OID of the database where a dependent object is (0 for a shared object) |
classid |
oid |
oid in PG_CLASS |
OID of the system catalog where a dependent object resides |
objid |
oid |
Any OID column |
OID of the dependent object |
objsubid |
integer |
- |
Column number for a table column (objid and classid refer to the table itself); The value is 0 for all other object types. |
refclassid |
oid |
oid in PG_CLASS |
OID of the system catalog (must be a shared catalog) where a referenced object is located. |
refobjid |
oid |
Any OID column |
OID of the referenced object |
deptype |
"char" |
- |
Code segment defining the specific semantics of this dependency relationship. See the following for details. |
objfile |
text |
- |
Path of a user-defined function library file |
- SHARED_DEPENDENCY_OWNER (o)
The referenced object (which must be a role) is the owner of the dependent object.
- SHARED_DEPENDENCY_ACL (a)
The referenced object (which must be a role) is mentioned in the access control list (ACL) of the dependent object. SHARED_DEPENDENCY_ACL does not add a record to the owner of the object because the owner will have a SHARED_DEPENDENCY_OWNER record.
- SHARED_DEPENDENCY_PIN (p)
This type of record indicates that the system itself depends on the depended object. Therefore, such an object cannot be deleted. Entries of this type are created only by initdb. The columns for the dependent object contain zeroes.
- SHARED_DEPENDENCY_ DBPRIV(d)
The referenced object (must be a role) has the ANY permission on the dependent object (the specified OID of the dependent object corresponds to a row in the 13.2.11 GS_DB_PRIVILEGE system catalog).
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