postgresql.table.size
Table disk sizeDimensions:None
Interface Metrics (2)
Dimensions:None
Dimensions:None
Technical Annotations (16)
CLI Commands (9)
SELECT relname, n_live_tup, n_dead_tup, pg_size_pretty(pg_total_relation_size(oid)) FROM pg_stat_user_tables WHERE schemaname = 'public';diagnosticVACUUM FULL table_name;remediationSELECT schemaname, relname, pg_size_pretty(pg_total_relation_size(schemaname || '.' || relname)) as size FROM pg_stat_user_tables ORDER BY pg_total_relation_size(schemaname || '.' || relname) DESC LIMIT 10;diagnosticVACUUM ANALYZE;remediationVACUUM FULL my_large_table;remediationSELECT relpages, reltuples FROM pg_class WHERE relname='table_name'diagnosticCREATE TABLE events (...) PARTITION BY RANGE (created_at);remediationCREATE TABLE events_2026_01 PARTITION OF events FOR VALUES FROM ('2026-01-01') TO ('2026-02-01');remediationSELECT partman.create_parent('public.events', 'created_at', 'native', 'monthly', p_premake := 3);remediationTechnical References (7)
dead tuplesconceptVACUUM FULLcomponentautovacuumcomponentmain table forkcomponentpg_partmancomponentPARTITION BY RANGEconceptpartition pruningconceptRelated Insights (4)
Dead tuples accumulate massively when autovacuum is blocked from cleanupcritical
▸
Table bloat consuming excessive disk spacewarning
▸
Table bloat increases sequential scan cost linearlywarning
▸
Large table sequential scans degrade at 100M+ rows despite proper indexingwarning
▸