The PostgreSQL Databases page lists databases discovered on a monitored PostgreSQL server. Use it to review database inventory and begin database-focused troubleshooting.
The Databases page gives context for a monitored PostgreSQL server before you start deeper troubleshooting. Use it to confirm which databases Mini DBA discovered, whether you are viewing the correct environment, and which database owns the workload you are investigating.
Database inventory is important on shared PostgreSQL servers because several applications may use the same instance. If an alert, query, or log entry references a database name, confirm the target here before opening PostgreSQL Activity, PostgreSQL Queries, or PostgreSQL Indexes.
If a database is missing, check the connection target, role privileges, cloud provider restrictions, and collection status. The setup guidance in Connect To PostgreSQL explains the monitoring role and host OS login options.
It is mainly inventory and context. Use Activity, Queries, Waits, Indexes, and Health Checks for tuning evidence.
The monitoring role may not have visibility, collection may not have completed, or the connection may target a different server.
Yes. It can support database inventory review when combined with Reports and Enterprise View.
After selecting the relevant PostgreSQL database, move to the evidence page that matches the symptom. Use Activity for current sessions, Queries for statement cost, Waits for delay patterns, Indexes for schema support, and Logs for server messages. If a database appears missing, review the connection target and monitoring role grants.