postgresql-performance-check

Diagnose PostgreSQL slow queries and lock contention by analyzing cluster load, active queries, and vacuum health. This requires kubectl access to your Kubernetes namespace running the PostgreSQL deployment to generate a comprehensive performance overview.

PostgreSQL autovacuum bottlenecks stem from transaction ID wraparound or heavy table bloat. Check vacuum health by analyzing per-database autovacuum status and cache efficiency to identify specific databases requiring targeted remediation.

pg_stat_statements is an optional PostgreSQL extension required to collect query-level statistics. While not strictly mandatory, enabling it provides detailed query-level insights necessary for accurately identifying slow queries.

Check cache efficiency and active queries by running a performance analysis against your running PostgreSQL instance. This process evaluates load distribution and query execution metrics to pinpoint performance bottlenecks.

Yes, this performance check is specifically applicable to running PostgreSQL instances in Kubernetes managed by pgskipper-operator. It analyzes cluster health and provides targeted remediation steps for tuning deployments.

Without query-level statistics from pg_stat_statements, PostgreSQL performance analysis is limited to load, lock contention, and vacuum health. You will miss detailed query-level metrics needed to identify specific slow queries.