PostgreSQL worst practices
summary
Advocates a shuffled deck of over 100 concrete misconfigurations, sampling ~10 per session with a small script, and illustrates damage with reproducible examples (a 10-row demo for “do not use indexes”). Recommends and mocks specific bad moves: turn autovacuum off, use JSONB for everything, write custom replication like Slony, use replication as the only backup, create dozens of indexes, set max_connections into the thousands instead of using pgbouncer, and choose timestamp without time zone.
AI-written summary · about
chapters (12)
- 0:00Introduction to bad habits
- 3:48Basic configuration errors
- 5:38Query and schema pitfalls
- 7:18Architecture and data modeling
- 10:46Indexing and backup failures
- 12:36Maintenance and data bloat
- 14:15Replication and failover
- 16:50Integrity and custom forks
- 18:45Transaction and code abuse
- 22:48Parameter and tuning errors
- 25:11Advanced traps and conclusion
- 29:34Q&A session
related talks
47mPostgreSQL worst practices
01h 00mThe 10 Deadly PostgreSQL Sins
35mThe PostgreSQL Twin Bill: The 7 Deadly PostgreSQL Mistakes & Review of What's New in PostgreSQL 14
51mHow Postgres is misused and abused in the wild
50mPostgreSQL gotchas for app developers
37mWhen it all goes Wrong (with Postgres)
42mPostgres: stories that will scare you
46mPostgres Platform "Best Practices" for the Modern DBA