ps, top, htop, and system monitoring dashboards. This is particularly valuable for DBAs managing multiple environments (development, staging, production) on the same infrastructure.'production-primary', 'analytics-replica', or 'app1-development'. Use consistent naming conventions across your organization. Avoid special characters or spaces that might cause issues with monitoring tools. The name should be meaningful enough to identify the cluster without additional context.ps and top will show the active query instead of just generic "postgres" process names. However, this comes with a small performance overhead due to the constant title updates.on is recommended for development and staging environments where debugging visibility is important. For production systems, evaluate the performance overhead—typically minimal—against the operational benefits. Consider setting to off in high-throughput production environments if you have alternative monitoring solutions. When enabled, be aware that very long queries may be truncated in process listings.Start your journey toward a healthier PostgreSQL with pghealth.
You can explore all features immediately with a free trial — no installation required.