FAQ
Is this monitoring? No. It is a point-in-time diagnosis. Run it when you need it. Scheduled scans are on the roadmap.
Will it slow my database down? The queries read statistics views and finish in seconds, with a 15 second statement timeout per query.
Why is my report nearly empty? Statistics may have been reset recently (restart, failover, serverless suspend). Run it again after a representative workload.
Can you show my Postgres logs? Not the log files: Postgres doesn't expose them over SQL on most providers. The Logs & activity section shows what the database itself tracks (rollbacks, deadlocks, temp files, checkpoints, archiver) and how logging is configured. For the log files, use your provider's log viewer or pgBadger.
Do you support replicas? You can scan a replica; replication-slot checks that need the primary are skipped.
Which Postgres versions? PostgreSQL 12 or newer. The command-line checkup is tested against 12 to 17.
Can I run it without giving you my connection string? Yes. npx pg-checkup scan runs on your machine and uploads a file of statistics only if you say so. See Run it on your machine.
Do you ever read my data? A checkup never does: it reads statistics and catalog metadata only. See Security & privacy.