database-development

Reversible database migrations require explicit up/down behavior with lock-aware rollback planning. You must verify successful up/down tests on a production-like environment, ensuring schema changes can roll back safely without disrupting table access.

Optimize slow queries by reviewing EXPLAIN ANALYZE output to confirm index usage rather than guessing. Adjust indexing strategies based on expected query plans, and verify slow query log cleanliness after changes to validate performance improvements in production.

Row-level security (RLS) for Postgres applies access control policies directly at the database layer. You implement RLS policies and validate both allow and deny paths using tests, ensuring users only access rows they are explicitly permitted to read or modify.

Yes, you verify backup restore procedures by completing a full restore rehearsal. This confirms your database recovery process meets your defined Recovery Time Objective (RTO), ensuring production data can be restored within required time constraints.

You need a read-only-by-default posture when designing safe database schemas and access controls. This approach requires explicit approval for writes, defaulting toward safer access patterns that protect production data from unintended or unauthorized modifications.