Typical application mistakes that lead to bloat in PostgreSQL
summary
The talk examines common application-design and coding mistakes that cause table/index bloat in PostgreSQL, explaining how specific practices during development lead to bloat and consequent performance degradation. It focuses on concrete examples of those mistakes and their effects on PostgreSQL storage and performance.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:14Long transactions and consequences
- 12:01How autovacuum works
- 19:47Load balancing mistakes
- 29:19Data migration problems
- 35:44Tools to fight bloat
- 40:05Q&A
related talks
53mTop Development Mistakes When Working with PostgreSQL
47mPostgreSQL worst practices
25mUnderstanding & Managing Postgres Table Bloat
46mHow PostgreSQL Can Hurt You When You Least Expect It
51mPostgreSQL: Practical Examples of SQL Query Optimization
50mPostgreSQL gotchas for app developers
50mAnomalies Under Load in PostgreSQL 2.0
01h 00mThe 10 Deadly PostgreSQL Sins
