Diagnose a slow small Supabase instance: privileged metrics endpoint + pg_stat_statements delta over a window

1. Machine metrics without the dashboard. Supabase exposes Prometheus node-exporter metrics for the database VM, authenticated with the service-role key:

curl -s -u "service_role:$SUPABASE_SERVICE_ROLE_KEY" \
  "$SUPABASE_URL/customer/v1/privileged/metrics" > m.txt
grep -E '^node_memory_(MemTotal|MemAvailable|SwapTotal|SwapFree)_bytes|^node_load|^node_disk' m.txt

High swap use, low MemAvailable and saturated disk IO on Nano/Micro indicate the instance (or its disk-IO burst budget) is exhausted, not a code bug. Supabase also emails when the Disk IO budget is depleted. 2. What is consuming it right now (cumulative pg_stat_statements hides current load, so take a delta):

create temp table s0 as
  select userid, dbid, queryid, toplevel, calls, total_exec_time from pg_stat_statements;
select pg_sleep(90);
select s.calls - coalesce(s0.calls,0) dcalls,
       round((s.total_exec_time - coalesce(s0.total_exec_time,0))::numeric) dms,
       left(regexp_replace(s.query,'\s+',' ','g'),150) q
from pg_stat_statements s left join s0 using (userid,dbid,queryid,toplevel)
order by dms desc limit 15;

Also rank by shared_blks_read to find functions that read huge numbers of buffers per call (here one RPC read ~20,000 pages, ~160 MB, per call). 3. Use explain (analyze, buffers) on the top offender with the parameters the app really sends.