01 /Tag — Postgresql
6 articles in this topic.
Add PostgreSQL indexes from observed filters, joins, ordering, and query plans while checking write cost, representative data, and deployment impact.
Handle simultaneous customer-record edits with explicit conflict policy, version checks or locking where appropriate, and tests that preserve both user intent and audit history.
Plan PostgreSQL tenant isolation with explicit ownership fields, trusted request context, runtime-role review, and tests covering joins, exports, and workers.
Review a SaaS database for an enterprise pilot through tenant boundaries, recovery evidence, schema change control, observability, and customer-specific operating requirements.
Plan database migrations around old and new application compatibility, bounded backfills, lock impact, verification, and recovery instead of a single deploy-time schema change.
Test SaaS database restores with an isolated recovery environment, known fixture records, application verification, measured recovery steps, and explicit file-store dependencies.