1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
HREF="mailto:pgsql-docs@postgresql.org"><LINK
12
TITLE="PostgreSQL 9.1beta1 Documentation"
13
HREF="index.html"><LINK
15
TITLE="System Catalogs"
16
HREF="catalogs.html"><LINK
19
HREF="catalog-pg-seclabel.html"><LINK
21
TITLE="pg_shdescription"
22
HREF="catalog-pg-shdescription.html"><LINK
25
HREF="stylesheet.css"><META
26
HTTP-EQUIV="Content-Type"
27
CONTENT="text/html; charset=ISO-8859-1"><META
29
CONTENT="2011-04-27T21:20:33"></HEAD
35
SUMMARY="Header navigation table"
47
>PostgreSQL 9.1beta1 Documentation</A
57
HREF="catalog-pg-seclabel.html"
66
TITLE="System Catalogs"
74
>Chapter 45. System Catalogs</TD
80
TITLE="System Catalogs"
89
TITLE="pg_shdescription"
90
HREF="catalog-pg-shdescription.html"
104
NAME="CATALOG-PG-SHDEPEND"
115
dependency relationships between database objects and shared objects,
116
such as roles. This information allows
120
> to ensure that those objects are
121
unreferenced before attempting to delete them.
125
HREF="catalog-pg-depend.html"
131
which performs a similar function for dependencies involving objects
132
within a single database.
135
> Unlike most system catalogs, <TT
139
is shared across all databases of a cluster: there is only one
161
><COL><COL><COL><COL><THEAD
189
HREF="catalog-pg-database.html"
197
>The OID of the database the dependent object is in,
198
or zero for a shared object</TD
215
HREF="catalog-pg-class.html"
223
>The OID of the system catalog the dependent object is in</TD
239
>The OID of the specific dependent object</TD
255
> For a table column, this is the column number (the
263
table itself). For all other object types, this column is zero.
281
HREF="catalog-pg-class.html"
289
>The OID of the system catalog the referenced object is in
290
(must be a shared catalog)</TD
306
>The OID of the specific referenced object</TD
322
> A code defining the specific semantics of this dependency relationship; see text
329
> In all cases, a <TT
332
> entry indicates that
333
the referenced object cannot be dropped without also dropping the dependent
334
object. However, there are several subflavors identified by
348
>SHARED_DEPENDENCY_OWNER</TT
355
> The referenced object (which must be a role) is the owner of the
362
>SHARED_DEPENDENCY_ACL</TT
369
> The referenced object (which must be a role) is mentioned in the
370
ACL (access control list, i.e., privileges list) of the
371
dependent object. (A <TT
373
>SHARED_DEPENDENCY_ACL</TT
375
not made for the owner of the object, since the owner will have
378
>SHARED_DEPENDENCY_OWNER</TT
385
>SHARED_DEPENDENCY_PIN</TT
392
> There is no dependent object; this type of entry is a signal
393
that the system itself depends on the referenced object, and so
394
that object must never be deleted. Entries of this type are
398
>. The columns for the
399
dependent object contain zeroes.
406
Other dependency flavors might be needed in future. Note in particular
407
that the current definition only supports roles as referenced objects.
415
SUMMARY="Footer navigation table"
426
HREF="catalog-pg-seclabel.html"
444
HREF="catalog-pg-shdescription.html"
473
>pg_shdescription</TT
b'\\ No newline at end of file'