Varqeni Help

Read PostgreSQL health

Updated 11 November 2026

A database can hurt every pipeline and application on it without any connector failing. Varqeni reads the server through the same read-only login the pipelines use, with fixed queries, and names what is wrong.

AvailabilityAvailable to everyone with early access to Varqeni.

Steps

  • Choose the database under Systems, or from the views.
  • What it reads: sessions with a transaction open for a long time, idle or running (never the query text), replication slots and whether anything reads them, prepared transactions, transaction ID age per database, connections in use against the server's limit, and the tables with the most dead rows.
  • What it names: a long running transaction, a session idle inside an open transaction, a replication slot nobody reads, connections close to the limit, and a database it cannot reach. Each names the session, slot or database to act on.
  • What it does: recommends only. Varqeni never ends a session, drops a slot or runs VACUUM; a person does, after asking the session's owner.
  • In the lab it named the cause in 30 of 30 blind trials. Transaction ID wraparound and old prepared transactions are checked too, but cannot be made in the lab, so they are tested in code only.

What you should see: The database card shows connections in use, open transactions, slots, the oldest transaction ID by database and dead rows.

What it can and cannot do

Can

  • Read the PostgreSQL server itself and name a long or idle transaction, a slot nobody reads, connections near the limit or a database it cannot reach.

Cannot

  • End a session, drop a slot or run VACUUM: it recommends only.

Still stuck? Contact support or email info@fortisdatagroup.com.