提交 733e25c7 编写于 作者: C Chuck Litzell 提交者: David Yozie

Docs - update pg_class and pg_index catalog table references (#7504)

* Docs - update pg_class and pg_index catalog table references

* dyozie review comments
上级 eb130b16
......@@ -130,31 +130,6 @@
<codeph>0</codeph> if none. The TOAST table stores large attributes "out of line" in
a secondary table.</entry>
</row>
<row>
<entry colname="col1">
<codeph>reltoastidxid</codeph>
</entry>
<entry colname="col2">oid</entry>
<entry colname="col3">pg_class.oid</entry>
<entry colname="col4">For a TOAST table, the OID of its index. <codeph>0</codeph> if not
a TOAST table.</entry>
</row>
<row>
<entry colname="col1">
<codeph>relaosegidxid</codeph>
</entry>
<entry colname="col2">oid</entry>
<entry colname="col3"/>
<entry colname="col4">Deprecated <ph>in Greenplum Database 3.4</ph>.</entry>
</row>
<row>
<entry colname="col1">
<codeph>relaosegrelid</codeph>
</entry>
<entry colname="col2">oid</entry>
<entry colname="col3"/>
<entry colname="col4">Deprecated<ph> in Greenplum Database 3.4</ph>.</entry>
</row>
<row>
<entry colname="col1">
<codeph>relhasindex </codeph>
......@@ -224,38 +199,6 @@
<entry colname="col3"/>
<entry colname="col4">Number of check constraints on the table.</entry>
</row>
<row>
<entry colname="col1">
<codeph>reltriggers</codeph>
</entry>
<entry colname="col2">int2</entry>
<entry colname="col3"/>
<entry colname="col4">Number of triggers on the table.</entry>
</row>
<row>
<entry colname="col1">
<codeph>relukeys</codeph>
</entry>
<entry colname="col2">int2</entry>
<entry colname="col3"/>
<entry colname="col4">Unused</entry>
</row>
<row>
<entry colname="col1">
<codeph>relfkeys</codeph>
</entry>
<entry colname="col2">int2</entry>
<entry colname="col3"/>
<entry colname="col4">Unused</entry>
</row>
<row>
<entry colname="col1">
<codeph>relrefs</codeph>
</entry>
<entry colname="col2"> int2</entry>
<entry colname="col3"/>
<entry colname="col4">Unused</entry>
</row>
<row>
<entry colname="col1">
<codeph>relhasoids</codeph>
......@@ -294,6 +237,25 @@
<entry colname="col3"/>
<entry colname="col4">True if table has (or once had) any inheritance children.</entry>
</row>
<row>
<entry>
<codeph>relispopulated</codeph>
</entry>
<entry>
boolean
</entry>
<entry></entry>
<entry>True if relation is populated (this is true for all relations other than some
materialized views).</entry>
</row>
<row>
<entry><codeph>relreplident</codeph></entry>
<entry>char</entry>
<entry></entry>
<entry>Columns used to form “replica identity” for rows: d = default (primary key, if
any), n = nothing, f = all columns i = index with <codeph>indisreplident</codeph> set, or
default</entry>
</row>
<row>
<entry colname="col1">
<codeph>relfrozenxid</codeph>
......@@ -303,11 +265,21 @@
<entry colname="col4">All transaction IDs before this one have been replaced with a
permanent (frozen) transaction ID in this table. This is used to track whether the
table needs to be vacuumed in order to prevent transaction ID wraparound or to allow
<codeph>pg_clog</codeph> to be shrunk. <p>The value is <codeph>0</codeph>
(<codeph>InvalidTransactionId</codeph>) if the relation is not a table or if the
<codeph>pg_clog</codeph> to be shrunk. <p>The value is <codeph>0</codeph>
(<codeph>InvalidTransactionId</codeph>) if the relation is not a table or if the
table does not require vacuuming to prevent transaction ID wraparound. The table
still might require vacuuming to reclaim disk space.</p></entry>
</row>
<row>
<entry><codeph>relminmxid</codeph></entry>
<entry>xid</entry>
<entry></entry>
<entry>All multixact IDs before this one have been replaced by a transaction ID in this
table. This is used to track whether the table needs to be vacuumed in order to
prevent multixact ID wraparound or to allow <codeph>pg_multixact</codeph> to be
shrunk. Zero (<codeph>InvalidMultiXactId</codeph>) if the relation is not a
table.</entry>
</row>
<row>
<entry colname="col1">
<codeph>relacl</codeph>
......@@ -315,7 +287,7 @@
<entry colname="col2"> aclitem[]</entry>
<entry colname="col3"/>
<entry colname="col4">Access privileges assigned by <codeph>GRANT</codeph> and
<codeph>REVOKE</codeph>.</entry>
<codeph>REVOKE</codeph>.</entry>
</row>
<row>
<entry colname="col1">
......
......@@ -65,6 +65,19 @@
<entry colname="col4">If true, this index represents the primary key of the table.
(indisunique should always be true when this is true.)</entry>
</row>
<row>
<entry><codeph>indisexclusion</codeph></entry>
<entry>boolean</entry>
<entry/>
<entry>If true, this index supports an exclusion constraint</entry>
</row>
<row>
<entry>indimmediate</entry>
<entry>boolean</entry>
<entry/>
<entry>If true, the uniqueness check is enforced immediately on insertion (irrelevant if
<codeph>indisunique</codeph> is not true)</entry>
</row>
<row>
<entry colname="col1">
<codeph>indisclustered</codeph>
......@@ -85,17 +98,54 @@
<codeph>INSERT</codeph>/<codeph>UPDATE</codeph> operations, but it cannot safely be
used for queries.</entry>
</row>
<row>
<entry><codeph>indcheckxmin</codeph></entry>
<entry>boolean</entry>
<entry/>
<entry>If true, queries must not use the index until the <codeph>xmin</codeph> of this
<codeph>pg_index</codeph> row is below their <codeph>TransactionXmin</codeph> event
horizon, because the table may contain broken HOT chains with incompatible rows that
they can see</entry>
</row>
<row>
<entry><codeph>indisready</codeph></entry>
<entry>boolean</entry>
<entry/>
<entry>If true, the index is currently ready for inserts. False means the index must be
ignored by <codeph>INSERT</codeph>/<codeph>UPDATE</codeph> operations</entry>
</row>
<row>
<entry><codeph>indislive</codeph></entry>
<entry>boolean</entry>
<entry/>
<entry>If false, the index is in process of being dropped, and should be ignored for all
purposes </entry>
</row>
<row>
<entry><codeph>indisreplident</codeph></entry>
<entry>boolean</entry>
<entry/>
<entry>If true this index has been chosen as "replica identity" using <codeph>ALTER
TABLE ... REPLICA IDENTITY USING INDEX ...</codeph></entry>
</row>
<row>
<entry colname="col1">
<codeph>indkey</codeph>
</entry>
<entry colname="col2">int2vector</entry>
<entry colname="col3">pg_attribute.attnum</entry>
<entry colname="col4">This is an array of indnatts values that indicate which table
columns this index indexes. For example a value of 1 3 would mean that the first and
the third table columns make up the index key. A zero in this array indicates that the
corresponding index attribute is an expression over the table columns, rather than a
simple column reference.</entry>
<entry colname="col4">This is an array of <codeph>indnatts</codeph> values that indicate
which table columns this index indexes. For example a value of 1 3 would mean that the
first and the third table columns make up the index key. A zero in this array
indicates that the corresponding index attribute is an expression over the table
columns, rather than a simple column reference.</entry>
</row>
<row>
<entry><codeph>indcollation</codeph></entry>
<entry>oidvector</entry>
<entry/>
<entry>For each column in the index key, this contains the OID of the collation to use
for the index.</entry>
</row>
<row>
<entry colname="col1">
......@@ -106,6 +156,13 @@
<entry colname="col4">For each column in the index key this contains the OID of the
operator class to use.</entry>
</row>
<row>
<entry><codeph>indoption</codeph></entry>
<entry>int2vector</entry>
<entry/>
<entry>This is an array of <codeph>indnatts</codeph> values that store per-column flag
bits. The meaning of the bits is defined by the index's access method.</entry>
</row>
<row>
<entry colname="col1">
<codeph>indexprs</codeph>
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册