(references pg_class.oid)
- The OID of the <structname>pg_class> entry for this sequence
+ The OID of the <link linkend="catalog-pg-class">pg_class> entry for this sequence
The catalog pg_statistic_ext_data
- holds data for extended planner statistics defined in pg_statistic_ext.
+ holds data for extended planner statistics defined in
+ pg_statistic_ext.
Each row in this catalog corresponds to a statistics object
created with .
- Like <structname>pg_statistic>,
+ Like <link linkend="catalog-pg-statistic">pg_statistic>,
pg_statistic_ext_data should not be
readable by the public, since the contents might be considered sensitive.
(Example: most common combinations of values in columns might be quite
pg_stats_ext
is a publicly readable view
on pg_statistic_ext_data (after joining
- with <structname>pg_statistic_ext>) that only exposes
+ with <link linkend="catalog-pg-statistic-ext">pg_statistic_ext>) that only exposes
information about those tables and columns that are readable by the
current user.
(references pg_constraint.oid)
- The <structname>pg_constraint> entry associated with the trigger, if any
+ The <link linkend="catalog-pg-constraint">pg_constraint> entry associated with the trigger, if any
When tgconstraint is nonzero,
tgconstrrelid, tgconstrindid,
tgdeferrable, and tginitdeferred are
- largely redundant with the referenced <structname>pg_constraint> entry.
+ largely redundant with the referenced <link linkend="catalog-pg-constraint">pg_constraint> entry.
However, it is possible for a non-deferrable trigger to be associated
with a deferrable constraint: foreign key constraints can have some
deferrable and some non-deferrable triggers.
(references pg_ts_config.oid)
- The OID of the <structname>pg_ts_config> entry owning this map entry
+ The OID of the <link linkend="catalog-pg-ts-config">pg_ts_config> entry owning this map entry
If this is a composite type (see
typtype), then this column points to
- the <structname>pg_class> entry that defines the
+ the <link linkend="catalog-pg-class">pg_class> entry that defines the
corresponding table. (For a free-standing composite type, the
- <structname>pg_class> entry doesn't really represent
+ <link linkend="catalog-pg-class">pg_class> entry doesn't really represent
a table, but it is needed anyway for the type's
- <structname>pg_attribute> entries to link to.)
+ <link linkend="catalog-pg-attribute">pg_attribute> entries to link to.)
Zero for non-composite types.
The view pg_hba_file_rules provides a summary of
- the contents of the client authentication configuration
- file, pg_hba.conf. A row appears in this view for each
+ the contents of the client authentication configuration file,
+ pg_hba.conf.
+ A row appears in this view for each
non-empty, non-comment line in the file, with annotations indicating
whether the rule could be applied successfully.
individual tuples of relations,
transaction IDs (both virtual and permanent IDs),
and general database objects (identified by class OID and object OID,
- in the same way as in <structname>pg_description> or
- <structname>pg_depend>). Also, the right to extend a
+ in the same way as in <link linkend="catalog-pg-description">pg_description> or
+ <link linkend="catalog-pg-depend">pg_depend>). Also, the right to extend a
relation is represented as a separate lockable object, as is the right to
update pg_database.datfrozenxid.
Also, advisory
locks can be taken on numbers that have
pg_locks provides a global view of all locks
in the database cluster, not only those relevant to the current database.
Although its relation column can be joined
- against <structname>pg_class>.oid to identify locked
+ against <link linkend="catalog-pg-class">pg_class>.oid to identify locked
relations, this will only work correctly for relations in the current
database (those for which the database column
is either the current database's OID or zero).
The view pg_publication_tables provides
information about the mapping between publications and the tables they
- contain. Unlike the underlying
- catalog pg_publication_rel, this view expands
+ contain. Unlike the underlying catalog
+ pg_publication_rel,
+ this view expands
publications defined as FOR ALL TABLES, so for such
publications there will be a row for each eligible table.
The pg_rules view excludes the ON SELECT rules
of views and materialized views; those can be seen in
- <structname>pg_views and pg_matviews>.
+ <link linkend="view-pg-views">pg_views and pg_matviews>.
the information stored in the
linkend="catalog-pg-statistic">pg_statistic
catalog. This view allows access only to rows of
- <structname>pg_statistic> that correspond to tables the
+ <link linkend="catalog-pg-statistic">pg_statistic> that correspond to tables the
user has permission to read, and therefore it is safe to allow public
read access to this view.
pg_stats is also designed to present the
information in a more readable format than the underlying catalog
— at the cost that its schema must be extended whenever new slot types
- are defined for <structname>pg_statistic>.
+ are defined for <link linkend="catalog-pg-statistic">pg_statistic>.
linkend="catalog-pg-statistic-ext">pg_statistic_ext
and pg_statistic_ext_data
catalogs. This view allows access only to rows of
- <structname>pg_statistic_ext and pg_statistic_ext_data>
+ <link linkend="catalog-pg-statistic-ext">pg_statistic_ext and pg_statistic_ext_data>
that correspond to tables the user has permission to read, and therefore
it is safe to allow public read access to this view.
pg_stats_ext is also designed to present the
information in a more readable format than the underlying catalogs
— at the cost that its schema must be extended whenever new types
- of extended statistics are added to <structname>pg_statistic_ext>.
+ of extended statistics are added to <link linkend="catalog-pg-statistic-ext">pg_statistic_ext>.
projects / postgresql.git / commitdiff