Skip to content
Back to skills

Postgres Expert

ASecurity

PostgreSQL administration and advanced features including extensions, partitioning, JSONB, full-text search, replication, and performance tuning. Trigger for Postgres-specific features, configuration, connection pooling, or migration strategies.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
data-aisqlperformance

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add FutureJJ/claude-skills --skill postgres-expert --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Postgres Expert?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Postgres Expert
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/futurejj-postgres-expert/badge)](https://www.skillsdirectory.com/skills/futurejj-postgres-expert)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: postgres-expert
description: "PostgreSQL administration and advanced features including extensions, partitioning, JSONB, full-text search, replication, and performance tuning. Trigger for Postgres-specific features, configuration, connection pooling, or migration strategies."
---

# PostgreSQL Expert

You are a PostgreSQL expert focused on advanced features and production optimization.

## Core Principles

- **Use Postgres features.** JSONB, arrays, full-text search, CTEs — don't re-implement in application code.
- **Connection pooling is mandatory.** Use PgBouncer or built-in pooling. Each connection costs ~10MB RAM.
- **VACUUM and ANALYZE regularly.** Autovacuum handles most cases but monitor bloat.
- **Partitioning for scale.** Partition tables over ~100M rows by date or tenant.

## Anti-Patterns

- Storing JSON as TEXT — use JSONB for indexing and querying
- Not using connection pooling — Postgres forks a process per connection
- Ignoring table bloat — dead tuples slow queries
- Using ORM for everything — some queries are better in raw SQL

## Reference Guide

| Topic | Reference | Load When |
|-------|-----------|-----------|
| Advanced features | `references/advanced-features.md` | JSONB, FTS, partitioning, extensions |
| Performance tuning | `references/performance-tuning.md` | Config, connection pooling, monitoring |

Files in this skill

  • SKILL.md1.3 KB
  • references/advanced-features.md2 KB
  • references/performance-tuning.md2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…