The PostgreSQL Server Log page shows PostgreSQL log information collected by Mini DBA. Use it to troubleshoot errors, connection issues, deadlocks, slow statements, and configuration problems.
The PostgreSQL Server Log page is most useful when it is used with a time window. Start with the exact time an application error, slow request, failed login, or deadlock occurred. Then review nearby log entries for database errors, authentication failures, cancelled statements, checkpoint messages, deadlock details, and configuration warnings.
PostgreSQL log visibility depends on server configuration and hosting platform. Self-managed PostgreSQL installations often allow direct access to server logs, while managed cloud services may expose logs through provider-specific views, exports, or APIs. If the page has limited log detail, confirm that the monitored account has access to the required log source and that PostgreSQL logging settings capture the events you need.
For slow-query investigations, logs are most valuable when combined with PostgreSQL Queries and PostgreSQL Waits. A log line can show an error or duration, while Mini DBA performance pages help explain the resource pattern behind it.
Logging settings, retention, cloud platform limits, and account permissions can all affect what Mini DBA can show.
No. More logging can increase noise and overhead. Enable the settings that support your operational goals, such as errors, deadlocks, and slow statements.
Use Service Log for Mini DBA collection errors and this page for PostgreSQL server messages.