transaction-management-specialist

What problem does it solve?

Ensures database operations are executed atomically and consistently to prevent race conditions, lost updates, dirty reads, and deadlocks during concurrent access in PostgreSQL and Supabase environments.

Core Features & Use Cases

• Atomic Transactions: Patterns and examples for BEGIN/COMMIT/ROLLBACK to keep multi-step operations all-or-nothing.
• Concurrency Control: Guidance on isolation levels, SELECT FOR UPDATE locking, optimistic locking with version columns, and deadlock avoidance.
• Reliability Techniques: Savepoints, deadlock retry strategies, idempotent upserts, monitoring long-running transactions, and using RPC/stored functions for safe server-side transactions.
• Use Case: Implementing money transfers, inventory reservations, and audit logging that must remain consistent under concurrent user load.

Quick Start

Use the transaction-management-specialist to implement a PostgreSQL transfer function that locks accounts in a consistent order, validates balances, and retries safely on serialization failures or deadlocks.