The 10 Deadly PostgreSQL Sins
summary
Ten recurring production mistakes and concrete fixes: using the wrong tool (eg pg_repack can block busy DDL), confusing pooling vs load‑balancing (use pgbouncer + HAProxy or pgpool2 depending on needs), and leaving defaults untuned (shared_buffers, work_mem, WAL/checkpoint sizes). Security lapses are common — ~1 in 10 incidents — and PostgreSQL 14 makes scram‑sha‑256 the default. Vacuum misconfigurations cause txid wraparound; connections cost tens of MB each; use Patroni for HA and pgBackRest with at least weekly fulls and 7‑day retention.
AI-written summary · about
chapters (8)
- 0:00Start
- 10:53Proper Use of Vacuum
- 15:12Poor Connection Management
- 17:14DEFAULT SETTINGS
- 22:46Extension Foo Because you can should
- 28:30HA & Backups
- 33:49the DB for the Workload
- 35:31the System for the Workload
related talks
35mThe PostgreSQL Twin Bill: The 7 Deadly PostgreSQL Mistakes & Review of What's New in PostgreSQL 14
36mPostgreSQL worst practices
47mPostgreSQL worst practices
51mHow Postgres is misused and abused in the wild
31m10 Costly Database Performance Mistakes (and How to Fix Them)
42mPostgres: stories that will scare you
57mPostgreSQL When It's Not Your Job
53mTop Development Mistakes When Working with PostgreSQL