postgres

Optimize PostgreSQL performance through query analysis, indexing, and safe schema migrations.

25|3|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill postgres-nimadorostkar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postgres
Source: https://github.com/nimadorostkar/Claude-Skills-collection/tree/main/skills/data/postgres
Command: npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill postgres-nimadorostkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the operational complexities of PostgreSQL, preventing common pitfalls like table bloat, lock contention, and inefficient query execution that degrade database performance.

Core Features & Use Cases

  • Performance Optimization: Identify and resolve slow queries using pg_stat_statements and optimize indexing strategies.
  • Operational Stability: Manage MVCC, autovacuum tuning, and connection pooling to ensure high availability.
  • Safe Migrations: Execute schema changes on large tables without downtime or blocking production traffic.

Quick Start

Use the postgres skill to analyze the current database schema and identify unused indexes that are causing write amplification.

Frequently Asked Questions about postgres

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

FAQPage Schema
How do I optimize slow PostgreSQL queries in high-traffic production environments?

Optimize slow PostgreSQL queries by analyzing execution plans with pg_stat_statements and refining indexing strategies. This targets high-traffic production environments to resolve inefficient query execution and improve database performance.

What is the best way to execute non-blocking schema migrations on large PostgreSQL tables?

The best way to execute non-blocking schema migrations is using lock-timeout safety during DDL operations. This ensures schema changes on large tables occur without downtime or blocking production traffic.

How does MVCC management and autovacuum tuning prevent table bloat in PostgreSQL?

MVCC management and autovacuum tuning prevent table bloat by managing obsolete tuple versions efficiently. Proper configuration ensures operational stability and high availability by preventing lock contention and disk space exhaustion.

Can I identify unused indexes causing write amplification in my database?

Yes, you can identify unused indexes causing write amplification by analyzing the current database schema. This process removes unnecessary write overhead and significantly improves database performance.

When do I need connection pooling for PostgreSQL operational stability?

You need connection pooling for operational stability when managing high-traffic production environments. It manages MVCC overhead and ensures high availability by preventing connection exhaustion during concurrent database access.