![]() This is used to track whether the table needs to be vacuumed in order to prevent transaction ID wraparound or to allow pg_xact to be shrunk. That state is only visible internally this field should never contain anything other than zero for a user-visible relation.Īll transaction IDs before this one have been replaced with a permanent ( “ frozen”) transaction ID in this table. oid)įor new relations being written during a DDL operation that requires a table rewrite, this contains the OID of the original relation otherwise zero. True if relation is populated (this is true for all relations other than some materialized views)Ĭolumns used to form “ replica identity” for rows: d = default (primary key, if any), n = nothing, f = all columns, i = index with indisreplident set (same as nothing if the index used has been dropped) True if row-level security (when enabled) will also apply to table owner see pg_policy catalog True if table has row-level security enabled see pg_policy catalog True if table or index has (or once had) any inheritance children or partitions True if table has (or once had) triggers see pg_trigger catalog True if table has (or once had) rules see pg_rewrite catalog Number of CHECK constraints on the table see pg_constraint catalog ![]() There must be this many corresponding entries in pg_attribute. Number of user columns in the relation (system columns not counted). R = ordinary table, i = index, S = sequence, t = TOAST table, v = view, m = materialized view, c = composite type, f = foreign table, p = partitioned table, I = partitioned index P = permanent table/sequence, u = unlogged table/sequence, t = temporary table/sequence Only certain system catalogs (such as pg_database) are shared. True if this table is shared across all databases in the cluster. True if this is a table and it has (or recently had) any indexes The TOAST table stores large attributes “ out of line” in a secondary table. OID of the TOAST table associated with this table, zero if none. ![]() It is updated by VACUUM, ANALYZE, and a few DDL commands such as CREATE INDEX. This is only an estimate used by the planner. Number of pages that are marked all-visible in the table's visibility map. If the table has never yet been vacuumed or analyzed, reltuples contains -1 indicating that the row count is unknown. ![]() Size of the on-disk representation of this table in pages (of size BLCKSZ). (Not meaningful if the relation has no on-disk file.) If zero, the database's default tablespace is implied. The tablespace in which this relation is stored. Reltablespace oid (references pg_tablespace. Name of the on-disk file of this relation zero means this is a “ mapped” relation whose disk file name is determined by low-level state ![]() If this is a table or an index, the access method used (heap, B-tree, hash, etc.) otherwise zero (zero occurs for sequences, as well as relations without storage, such as views) The OID of the data type that corresponds to this table's row type, if any zero for indexes, sequences, and toast tables, which have no pg_type entryįor typed tables, the OID of the underlying composite type zero for all other relations The OID of the namespace that contains this relation Relnamespace oid (references pg_namespace. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |