PluginBench
Skill
Pass
Audit score 90

postgres-patterns

affaan-m/ecc

PostgreSQL best practices for indexing, schema design, query optimization, and security.

What is postgres-patterns?

Reference patterns for PostgreSQL database design and optimization based on Supabase best practices. Use when writing SQL queries, designing schemas, troubleshooting slow queries, implementing Row Level Security, or setting up connection pooling.

  • Index selection guide covering B-tree, composite, GIN, and BRIN indexes
  • Data type recommendations for IDs, strings, timestamps, money, and flags
  • Query patterns including composite indexes, covering indexes, partial indexes, and cursor pagination
  • Row Level Security policy optimization and UPSERT patterns
  • Anti-pattern detection queries for unindexed foreign keys, slow queries, and table bloat
  • PostgreSQL configuration template for connections, timeouts, and monitoring

How to install postgres-patterns

npx skills add null --skill postgres-patterns
Claude Code
Cursor
Windsurf
Cline

How to use postgres-patterns

  1. 1.Reference the Index Cheat Sheet when adding indexes to match your query patterns
  2. 2.Use the Data Type Quick Reference to select appropriate column types during schema design
  3. 3.Apply Common Patterns like composite indexes, covering indexes, and partial indexes to your schema
  4. 4.Run Anti-Pattern Detection queries to find unindexed foreign keys and slow queries in existing databases
  5. 5.Use the Configuration Template to set production-safe connection limits and timeouts
  6. 6.Consult the database-reviewer agent for comprehensive database reviews

Use cases

Good for
  • Choosing the right index type for WHERE clauses and range queries
  • Designing composite indexes to optimize multi-column filters
  • Implementing cursor-based pagination for O(1) performance instead of OFFSET
  • Setting up Row Level Security policies with optimized query wrapping
  • Detecting and fixing unindexed foreign keys and slow queries
Who it's for
  • Backend developers writing SQL migrations and queries
  • Database architects designing schemas and indexing strategies
  • DevOps engineers configuring PostgreSQL for production
  • Full-stack developers optimizing database performance

postgres-patterns FAQ

When should I use a composite index vs. separate indexes?

Use composite indexes when you have multi-column WHERE clauses with equality conditions first, then range conditions. Separate indexes are better for independent column queries.

Why use timestamptz instead of timestamp?

timestamptz stores timezone information and is unambiguous across regions, while timestamp is timezone-naive and can cause confusion in distributed systems.

What's the difference between cursor pagination and OFFSET?

Cursor pagination (WHERE id > $last_id) is O(1) and efficient for large datasets, while OFFSET scans all skipped rows making it O(n) and slow for deep pagination.

How do I optimize Row Level Security policies?

Wrap the auth check in a SELECT statement (SELECT auth.uid()) rather than calling it directly, which allows PostgreSQL to optimize the policy evaluation.

What should I do if I find unindexed foreign keys?

Create indexes on foreign key columns to improve JOIN performance and prevent sequential scans during referential integrity checks.

Full instructions (SKILL.md)

Source of truth, from affaan-m/ecc.


name: postgres-patterns description: PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices. metadata: origin: ECC

PostgreSQL Patterns

Quick reference for PostgreSQL best practices. For detailed guidance, use the database-reviewer agent.

When to Activate

  • Writing SQL queries or migrations
  • Designing database schemas
  • Troubleshooting slow queries
  • Implementing Row Level Security
  • Setting up connection pooling

Quick Reference

Index Cheat Sheet

Query PatternIndex TypeExample
WHERE col = valueB-tree (default)CREATE INDEX idx ON t (col)
WHERE col > valueB-treeCREATE INDEX idx ON t (col)
WHERE a = x AND b > yCompositeCREATE INDEX idx ON t (a, b)
WHERE jsonb @> '{}'GINCREATE INDEX idx ON t USING gin (col)
WHERE tsv @@ queryGINCREATE INDEX idx ON t USING gin (col)
Time-series rangesBRINCREATE INDEX idx ON t USING brin (col)

Data Type Quick Reference

Use CaseCorrect TypeAvoid
IDsbigintint, random UUID
Stringstextvarchar(255)
Timestampstimestamptztimestamp
Moneynumeric(10,2)float
Flagsbooleanvarchar, int

Common Patterns

Composite Index Order:

-- Equality columns first, then range columns
CREATE INDEX idx ON orders (status, created_at);
-- Works for: WHERE status = 'pending' AND created_at > '2024-01-01'

Covering Index:

CREATE INDEX idx ON users (email) INCLUDE (name, created_at);
-- Avoids table lookup for SELECT email, name, created_at

Partial Index:

CREATE INDEX idx ON users (email) WHERE deleted_at IS NULL;
-- Smaller index, only includes active users

RLS Policy (Optimized):

CREATE POLICY policy ON orders
  USING ((SELECT auth.uid()) = user_id);  -- Wrap in SELECT!

UPSERT:

INSERT INTO settings (user_id, key, value)
VALUES (123, 'theme', 'dark')
ON CONFLICT (user_id, key)
DO UPDATE SET value = EXCLUDED.value;

Cursor Pagination:

SELECT * FROM products WHERE id > $last_id ORDER BY id LIMIT 20;
-- O(1) vs OFFSET which is O(n)

Queue Processing:

UPDATE jobs SET status = 'processing'
WHERE id = (
  SELECT id FROM jobs WHERE status = 'pending'
  ORDER BY created_at LIMIT 1
  FOR UPDATE SKIP LOCKED
) RETURNING *;

Anti-Pattern Detection

-- Find unindexed foreign keys
SELECT conrelid::regclass, a.attname
FROM pg_constraint c
JOIN pg_attribute a ON a.attrelid = c.conrelid AND a.attnum = ANY(c.conkey)
WHERE c.contype = 'f'
  AND NOT EXISTS (
    SELECT 1 FROM pg_index i
    WHERE i.indrelid = c.conrelid AND a.attnum = ANY(i.indkey)
  );

-- Find slow queries
SELECT query, mean_exec_time, calls
FROM pg_stat_statements
WHERE mean_exec_time > 100
ORDER BY mean_exec_time DESC;

-- Check table bloat
SELECT relname, n_dead_tup, last_vacuum
FROM pg_stat_user_tables
WHERE n_dead_tup > 1000
ORDER BY n_dead_tup DESC;

Configuration Template

-- Connection limits (adjust for RAM)
ALTER SYSTEM SET max_connections = 100;
ALTER SYSTEM SET work_mem = '8MB';

-- Timeouts
ALTER SYSTEM SET idle_in_transaction_session_timeout = '30s';
ALTER SYSTEM SET statement_timeout = '30s';

-- Monitoring
CREATE EXTENSION IF NOT EXISTS pg_stat_statements;

-- Security defaults
REVOKE ALL ON SCHEMA public FROM public;

SELECT pg_reload_conf();

Related

  • Agent: database-reviewer - Full database review workflow
  • Skill: clickhouse-io - ClickHouse analytics patterns
  • Skill: backend-patterns - API and backend patterns

Based on Supabase Agent Skills (credit: Supabase team) (MIT License)