10 Costly Database Performance Mistakes (and How to Fix Them)
summary
Ten concrete mistakes cost teams time and money and each comes with fixes: 10 counted items, anchor migrations is released and lints SQL with squawk (it flags nonconcurrent indexes), a production clone and the copy swap drop pattern prove usable for big backfills, PG Analyze Lint finds a missing index on a rideshare table, and rollout tactics include trunkbased development backed by feature flags and rollup/materialized views to avoid massive deletes and huge result sets.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:30Infrequent releases hurt agility
- 5:18Database skill gaps
- 8:32Speculative design pitfalls
- 10:58Missing monitoring
- 13:05ORM query inefficiencies
- 16:36DDL fear and schema challenges
- 18:47Excessive data access
- 21:35Data archival strategies
- 24:43Missing maintenance
- 26:48Mechanical sympathy in design
related talks
01h 00mThe 10 Deadly PostgreSQL Sins
17mTop 10 transactional database mistakes, and how to avoid them
35mThe PostgreSQL Twin Bill: The 7 Deadly PostgreSQL Mistakes & Review of What's New in PostgreSQL 14
46mThe Top 10 Mistakes When Migrating Oracle Databases to PostgreSQL
47mPostgreSQL worst practices
36mPostgreSQL worst practices
53mTop Development Mistakes When Working with PostgreSQL
05mCommon mistakes of DBAs