postgresql-performance-check

Analyze PostgreSQL cluster load, queries, and vacuum health for bottlenecks.

1|3|Updated Mar 23, 2026

Search Tags:#performance #postgresql #autovacuum #vacuum #slow-queries #lock-contention

Ready to run

npx skills add https://github.com/IldarMinaev/troubleshooting-skill --skill postgresql-performance-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postgresql-performance-check
Source: https://github.com/IldarMinaev/troubleshooting-skill/tree/main/skills/postgresql-performance-check
Command: npx skills add https://github.com/IldarMinaev/troubleshooting-skill --skill postgresql-performance-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify PostgreSQL performance bottlenecks across a cluster by analyzing load, slow queries, and vacuum health to guide optimizations.

Core Features & Use Cases

Comprehensive performance overview: slow queries, active queries, and cache efficiency.
Lock contention and vacuum health analysis with per-database insights.
Targeted remediation steps and practical recommendations for tuning and fixes.

Quick Start

Run this skill against your Kubernetes-deployed PostgreSQL cluster to generate a comprehensive performance report.

Frequently Asked Questions about postgresql-performance-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose PostgreSQL slow queries and lock contention in Kubernetes?▼

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.

What causes PostgreSQL autovacuum bottlenecks and how can I check vacuum health?▼

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.

Do I need pg_stat_statements to analyze PostgreSQL query performance?▼

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.

How do I check cache efficiency and active queries on a running PostgreSQL instance?▼

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.

Can I use this approach to tune PostgreSQL deployments managed by pgskipper-operator?▼

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.

What are the limitations of analyzing PostgreSQL performance without query-level statistics?▼

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.