chore: add output examples for remaining

Author: loong

docs/supabase/inspect/cache-hit.md

@@ -2,10 +2,11 @@
 
 This command provides information on the efficiency of the buffer cache, for both index reads (`index hit rate`) as well as table reads (`table hit rate`). A low buffer cache hit ratio can be a sign that the Heroku Postgres plan is too small for the workload.
 
+TODO must mention what ratio is unhealthy
 
 ```
-      name      |         ratio
-----------------+------------------------
- index hit rate | 0.99957765013541945832
- table hit rate |                   1.00
+         NAME      │  RATIO
+  ─────────────────┼───────────
+    index hit rate │ 0.996621
+    table hit rate │ 0.999341
  ```

docs/supabase/inspect/outliers.md

@@ -4,6 +4,8 @@ This command displays statements, obtained from `pg_stat_statements`, ordered by
 
 Typically, an efficient query will have an appropriate ratio of calls to total execution time, with as little time spent on I/O as possible. Queries that have a high total execution time but low call count should be investigated to improve their performance. Queries that have a high proportion of execution time being spent on synchronous I/O should also be investigated.
 
+TODO check this table 👇
+
 ```
   
                  QUERY                   │ EXECUTION TIME   │ PROPORTION OF EXEC TIME │ NUMBER CALLS │ SYNC IO TIME

docs/supabase/inspect/seq-scans.md

@@ -9,8 +9,6 @@ This command displays the number of sequential scans recorded against all tables
     emails                           │ 182435
     users                            │  25063
     job_run_details                  │     60
-    schema_migrations                │      4
-    staging_resource_notifications   │      2
     schema_migrations                │      0
     migrations                       │      0
 ```

docs/supabase/inspect/supabase-schema-check.md

@@ -1 +1,14 @@
 # table-sizes
+
+This command displays the size of each table in the database. It is calculated by using the system administration function `pg_table_size()`, which includes the size of the main data fork, free space map, visibility map and TOAST data.
+
+
+```
+                  NAME               │    SIZE
+  ───────────────────────────────────┼─────────────
+    job_run_details                  │ 385 MB
+    emails                           │ 584 kB
+    job                              │ 40 kB
+    sessions                         │ 0 bytes
+    prod_resource_notifications_meta │ 0 bytes
+```

docs/supabase/inspect/table-sizes.md

@@ -1 +1,9 @@
 # total-index-size
+
+This command displays the total size of all indexes on the database. It is calculated by taking the number of pages (reported in `relpages`) and multiplying it by the page size (8192 bytes).
+
+```
+    SIZE
+  ─────────
+    12 MB
+```

docs/supabase/inspect/total-index-size.md

@@ -1,15 +1,11 @@
 ## total-table-sizes
 
-This command displays the total size of each table in the database, in MB. It is calculated by using the system administration function `pg_total_relation_size()`, which includes table size, total index size and TOAST data.
+This command displays the total size of each table in the database. It is calculated by using the system administration function `pg_total_relation_size()`, which includes table size, total index size and TOAST data.
 
 ```
                 NAME               │    SIZE
 ───────────────────────────────────┼─────────────
   job_run_details                  │ 395 MB
-  prod_resource_notifications      │ 299 MB
-  staging_resource_notifications   │ 47 MB
-  infra_alerts_to_delete           │ 18 MB
   slack_msgs                       │ 648 kB
-  dunning_emails                   │ 640 kB
-  project_emails                   │ 408 kB
+  emails                           │ 640 kB
 ```