Feature · /schema-monitoring
スキーマ監視
すべてのテーブル、カラム、インデックス — 変更履歴と帰属付きで監視。
In one line
スキーマ変更のタイムライン、インデックス健全性、ブロート、ドリフト、推奨インデックス。
What you get
- Schema change timeline — every CREATE / ALTER / DROP captured with attribution
- Index health: bloat ratio, scans-per-day, last used, duplicate detection
- Table stats: live tuples, dead tuples, last vacuum, last analyze, n_tup_ins/upd/del rates
- Drift alerts when staging and production schemas diverge
- Recommended indexes: signatures that would benefit from an index we don't have
FAQ
Does this work for managed databases (RDS, Aurora, Cloud SQL)?+
Yes. Schema introspection only needs read-level access to the catalog tables.
Related reading
Postgres
pg_stat_statements: the complete 2026 guide
Every column, every gotcha, the queries you should run today, and why pg_stat_statements is still the most useful 80 lines of telemetry in Postgres — even with five new alternatives in 2026.
MySQL
MySQL Performance Schema vs sys schema: a 2026 monitoring guide
Performance Schema is unreadable. sys schema is friendly but lossy. Here's exactly which to use for which production question, with the eight queries every MySQL DBA should know by heart.
Postgres
Postgres slow queries: 12 causes and how to find each one
A field-tested playbook for diagnosing a slow Postgres query in production — from missing indexes to plan flips to bloated tables — with the SQL to find each cause and the fix.