Skill

postgres-deep

PostgreSQL deep-dive: EXPLAIN ANALYZE interpretation, index types (B-tree, GIN, GiST, BRIN), partial/covering/composite indexes, pg_stat_statements slow query analysis, Row Level Security, window functions, CTEs, advisory locks, LISTEN/NOTIFY, connection pooling with PgBouncer. Use when optimizing slow queries, designing indexing strategy, implementing multi-tenancy.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

- Optimizing slow queries with EXPLAIN ANALYZE

Supporting Assets

references/connection-diagnostics.mdreferences/connection-pooling.mdreferences/index-tuning.mdreferences/indexing-strategies.mdreferences/partition-management.mdreferences/partitioning.mdreferences/query-anti-patterns.mdreferences/query-optimization.mdscripts/analyze-slow-queries.sh

SKILL.md

Similar Skills

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

postgres-deep

Core Principles

EXPLAIN ANALYZE before optimizing — never guess; measure first; the plan shows the actual cost

Index the access pattern, not the column — a composite index (user_id, created_at DESC) beats two separate indexes for paginated user queries

Partial indexes reduce size and maintenance cost — WHERE status = 'pending' on a 10M row table with 1000 pending rows = tiny, fast index

RLS is enforced at the DB layer — even if application code has a bug, unauthorized rows are invisible

pg_stat_statements is your slow query log — enable it; it shows cumulative query costs across all calls

References available

references/query-optimization.md — EXPLAIN ANALYZE interpretation, node types, warning signs, stale statistics, work_mem, CTEs

references/query-anti-patterns.md — N+1 queries, missing FK indexes, over-fetching, OFFSET pagination, NOT IN gotcha, DISTINCT misuse

references/indexing-strategies.md — B-tree, GIN, GiST, BRIN index types; composite and covering indexes; index type decision tree

references/index-tuning.md — partial indexes, expression indexes, index maintenance, unused/bloated index detection, CONCURRENTLY

references/partitioning.md — range/list/hash partitioning, when to partition, partition pruning, partitioned table constraints

references/partition-management.md — partition maintenance, DETACH/DROP/ATTACH, pg_partman automation, anti-patterns

references/connection-pooling.md — PgBouncer setup, pool modes (session/transaction/statement), pool sizing, application config

references/connection-diagnostics.md — SHOW POOLS, pg_stat_activity monitoring, connection troubleshooting runbook, Kubernetes deploy