skills.rest
jshsakura
jshsakuraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

postgres-pro

Identify PostgreSQL bottlenecks and propose rollback-safe fixes across schema, indexing, and replication.

22|2|Updated Mar 24, 2026
Search Tags:#performance#indexing#postgresql#migration#schema-design#locking
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill postgres-pro-jshsakura
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: postgres-pro
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/postgres-pro
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill postgres-pro-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when a task needs PostgreSQL-specific expertise for schema design, performance behavior, locking, or operational database features.

Core Features & Use Cases

  • Planner behavior with statistics, cardinality, and index selectivity considerations.
  • Lock modes, transaction isolation, and deadlock/contention risk assessment.
  • Schema evolution, migration/backfill safety on large tables, and vacuum/analyze implications.
  • Partitioning and replication/failover considerations for operational safety.

Quick Start

Run a focused PostgreSQL review on workload patterns to identify bottlenecks and propose minimal, rollback-safe changes.

Frequently Asked Questions about postgres-pro

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

FAQPage Schema
How do I identify PostgreSQL performance issues and locking bottlenecks in my workload?▼

PostgreSQL performance and locking issues are identified by evaluating workload patterns for planner behavior, lock modes, and index selectivity. This analysis targets schema design, vacuum/analyze, and partitioning to propose safe, high-leverage changes.

What is the safest way to execute schema migration and backfills on large PostgreSQL tables?▼

Schema migration on large PostgreSQL tables requires assessing backfill safety, lock isolation, and deadlock risk. This ensures changes account for transaction rollback implications and avoid blocking concurrent workloads.

How does PostgreSQL planner behavior affect index selectivity and query performance?▼

PostgreSQL planner behavior dictates query performance by evaluating statistics, cardinality, and index selectivity. Understanding this mechanism identifies when index design or vacuum/analyze adjustments resolve execution plan bottlenecks.

Can I evaluate partitioning and replication considerations for busy PostgreSQL databases?▼

Partitioning and replication considerations for busy PostgreSQL databases are evaluated to ensure operational safety during failover. This assesses how schema changes, locking, and vacuum operations impact replication lag and availability.

When should I not use a bulk index creation approach for PostgreSQL performance tuning?▼

Avoid bulk index creation when it introduces severe lock contention or deadlock risks on busy databases. Constraint analysis evaluates lock modes and transaction isolation to determine if backfills require safer, staggered, or rollback-ready approaches.

Related Skills

Explore More Software Engineering Skills→
AmidVoshakulAmidVoshakul

sql-pro

Analyze SQL execution plans and optimize indexing strategies for databases.

Community
Advanced
aolus-softwareaolus-software
1

postgresql

Guide PostgreSQL schema design with data types, constraints, indexing, and migration plans.

Official
Advanced
mohamed-g-shoaibmohamed-g-shoaib

postgres-pro

Analyze and optimize PostgreSQL performance, replication, and maintenance tasks.

Community
Advanced
shalevaminshalevamin

database-optimizer

Analyze execution plans and optimize PostgreSQL and MySQL database performance.

Community
Advanced