About pg-checkup

pg-checkup reads what PostgreSQL records about itself and tells you what to fix first, why, and how. It is built independently, for people who run PostgreSQL and want a straight answer.

Why it exists

PostgreSQL already records most of what goes wrong: dead rows that vacuum is not reaching, sequences close to their limit, queries that account for most of the load, policies that slow every read. That information sits in statistics views. Reading it takes time and experience, and reading it together is what points to the cause.

How we build it

• Read-only, on your machine. The checkup runs where you run it. The session cannot write, and your connection string is never sent to us.
• Findings in the order to fix them. There is no health score. A finding states what we observed, and says so when the evidence is too thin to name a cause.
• Free where it protects the database. Every finding, fix and SQL statement is free. Workspace pays for keeping history and watching on a schedule.
• Public PostgreSQL only. Every check is based on documented PostgreSQL behaviour and works the same on any provider.
• Readable where it counts. What touches your database ships as readable source, so you can check what runs and what leaves your machine.

Talk to us

Questions, bad findings and ideas all help. File a ticket or request a feature. We read all of it. We are also open to hearing from you if this is the kind of work you want to do.