STAT_ALL_TABLES
Displays the status of each table (including the TOAST table) on the current node of the database, as described in Table 1.
Name |
Type |
Description |
---|---|---|
relid |
oid |
OID of the table. |
schemaname |
name |
Name of the schema where the table is located. |
relname |
name |
Table name. |
seq_scan |
bigint |
Number of sequential scans initiated on the table. |
seq_tup_read |
bigint |
Number of live rows fetched by sequential scans. |
idx_scan |
bigint |
Number of index scans initiated on the table. |
idx_tup_fetch |
bigint |
Number of live rows fetched by index scans. |
n_tup_ins |
bigint |
Number of rows inserted. |
n_tup_upd |
bigint |
Number of rows updated. |
n_tup_del |
bigint |
Number of rows deleted. |
n_tup_hot_upd |
bigint |
Number of rows updated by HOT (that is, the number of rows whose index columns are not updated). |
n_live_tup |
bigint |
Estimated number of live rows. |
n_dead_tup |
bigint |
Estimated number of inactive rows. |
last_vacuum |
timestamp with time zone |
Last time at which this table was manually vacuumed (not counting VACUUM FULL). |
last_autovacuum |
timestamp with time zone |
Last time when the table was vacuumed by the autovacuum daemon thread. |
last_analyze |
timestamp with time zone |
Last time at which the table was manually analyzed. |
last_autoanalyze |
timestamp with time zone |
Last time when the table was analyzed by the autovacuum daemon thread. |
vacuum_count |
bigint |
Number of times that the table has been manually vacuumed (not counting VACUUM FULL). |
autovacuum_count |
bigint |
Number of times this table has been vacuumed by the autovacuum daemon. |
analyze_count |
bigint |
Number of times the table has been manually analyzed. |
autoanalyze_count |
bigint |
Number of times the table has been analyzed by the autovacuum daemon thread. |
last_updated |
timestamp with time zone |
Time when the monitoring data of the object in the view is updated for the last time. |
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