So You Inherited A Database
summary
Claims concrete steps to survive an inherited database: verify and test backups and SLAs, map inputs and consumers, build a data dictionary and push pg_description comments out to visible docs, hunt for PII in JSON and images, identify unused tables and columns, partition and age off cold data, and test replica failover. Demonstrated tactics include a partial unique index with timestamp floor to migrate uniqueness gradually and auditing materialized views refreshed at midnight to avoid hidden staleness.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:23Scaling Issues
- 10:01Your First Day on the Job
- 11:58Slas Service Level Agreements
- 13:03What Happens if the Database Is Offline
- 14:46Document Your Database
- 20:46Can You Limit the Valid Values in a Column
- 24:51Date Column
- 32:19Uniqueness
- 42:03Your Data Life Cycle
- 44:08Security
- 49:38Does Your Data Warehouse Happen in a Separate Database
- 51:31Closing Remarks
related talks
05mCommon mistakes of DBAs
48mMigrating to PostgreSQL: Strategies, Sovereignty, and Success
24mDatabases beyond the tutorials
59mPostgreSQL Don'ts and Dos
45mDebugging Databases for Developers
31mHelp! My Database Is The Bottleneck
50mAn ultimate guide to upgrading your PostgreSQL installation
36mUnlocking the Benefits of Database DevOps and Automation