supabase-postgres-best-practices
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
- License 许可
- MIT
- 最近更新
- 2026-08-25
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- supabase-postgres-best-practices
- license
- MIT
- metadata
- { "date": "January 2026", "author": "supabase", "version": "1.1.1", "abstract": "Comprehensive Postgres performance optimization guide for developers using Supabase and Postgres. Contains performance rules across 8 categories, prioritized by impact from critical (query performance, connection management) to incremental (advanced features). Each rule includes detailed explanations, incorrect vs. correct SQL examples, query plan analysis, and specific performance metrics to guide automated optimization and code generation.", "organization": "Supabase" }
- description
- Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
02 资源文件 35
- 参考文档CHANGELOG.md5.6 KB
- 参考文档references/_contributing.md4.0 KB
- 参考文档references/_sections.md1.6 KB
- 参考文档references/_template.md1.0 KB
- 参考文档references/advanced-full-text-search.md1.4 KB
- 参考文档references/advanced-jsonb-indexing.md1.4 KB
- 参考文档references/conn-idle-timeout.md1.3 KB
- 参考文档references/conn-limits.md1.3 KB
- 参考文档references/conn-pooling.md1.3 KB
- 参考文档references/conn-prepared-statements.md1.5 KB
- 参考文档references/data-batch-inserts.md1.3 KB
- 参考文档references/data-n-plus-one.md1.3 KB
- 参考文档references/data-pagination.md1.3 KB
- 参考文档references/data-upsert.md1.4 KB
- 参考文档references/lock-advisory.md1.5 KB
- 参考文档references/lock-deadlock-prevention.md1.8 KB
- 参考文档references/lock-short-transactions.md1.3 KB
- 参考文档references/lock-skip-locked.md1.3 KB
- 参考文档references/monitor-explain-analyze.md1.4 KB
- 参考文档references/monitor-pg-stat-statements.md1.4 KB
- 参考文档references/monitor-vacuum-analyze.md1.5 KB
- 参考文档references/query-composite-indexes.md1.4 KB
- 参考文档references/query-covering-indexes.md1.3 KB
- 参考文档references/query-index-types.md1.5 KB
- 参考文档references/query-missing-indexes.md1.2 KB
- 参考文档references/query-partial-indexes.md1.3 KB
- 参考文档references/schema-constraints.md1.8 KB
- 参考文档references/schema-data-types.md1.4 KB
- 参考文档references/schema-foreign-key-indexes.md1.6 KB
- 参考文档references/schema-lowercase-identifiers.md1.7 KB
- 参考文档references/schema-partitioning.md1.5 KB
- 参考文档references/schema-primary-keys.md1.8 KB
- 参考文档references/security-privileges.md1.5 KB
- 参考文档references/security-rls-basics.md1.3 KB
- 参考文档references/security-rls-performance.md2.1 KB
03 SKILL.md 正文
Supabase Postgres Best Practices
Local constraints
Query, connection, schema, lock, and type rules apply to any Postgres the current repo already runs.
- RLS,
pg_cron,pgmq, andpgvectoronly if the repo already has that extension or policy. Do not add them to a vanilla database to follow a rule. - Supabase dashboard, Auth, and Storage notes are optional. Ignore them off Supabase.
- After designing a new schema, start from
database-schema-designer, then come here for SQL shape.
When to Apply
Reference these guidelines when:
- Writing SQL queries or designing schemas
- Implementing indexes or query optimization
- Reviewing database performance issues
- Configuring connection pooling or scaling
- Optimizing for Postgres-specific features
- Working with Row-Level Security (RLS)
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Query Performance | CRITICAL | query- |
| 2 | Connection Management | CRITICAL | conn- |
| 3 | Security & RLS | CRITICAL | security- |
| 4 | Schema Design | HIGH | schema- |
| 5 | Concurrency & Locking | MEDIUM-HIGH | lock- |
| 6 | Data Access Patterns | MEDIUM | data- |
| 7 | Monitoring & Diagnostics | LOW-MEDIUM | monitor- |
| 8 | Advanced Features | LOW | advanced- |
How to Use
Read individual rule files for detailed explanations and SQL examples:
references/query-missing-indexes.md
references/query-partial-indexes.md
references/_sections.md
Each rule file contains:
- Brief explanation of why it matters
- Incorrect SQL example with explanation
- Correct SQL example with explanation
- Optional EXPLAIN output or metrics
- Additional context and references
- Supabase-specific notes (when applicable)
References
04 同仓库更多 Skills
writing-for-agents
Use for delegate_task, Kanban, and all agent-facing text.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
vue-best-practices
Use for Vue 3, .vue files, Vue Router, or Pinia. Skip when the repo has no Vue.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
tailwind-v4
Use when writing or reviewing Tailwind CSS v4 classes or migrating v3 syntax.
react-best-practices
Mastra React subset only. Generic React or Next uses vercel-react-best-practices.