How PostgreSQL Can Hurt You When You Least Expect It
summary
The talk examines PostgreSQL performance surprises that remain after normal query optimization, using several real incidents. It covers why index scan and index-only scan can be slow despite reasonable plans, reasons indexes may not be used, causes of unexpected table locking, and how latency between application and database can become a critical performance factor.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 11:36Global counters and MVCC
- 25:15Index problems
- 35:59Autovacuum and locks
- 41:44Summary
related talks
50mAnomalies Under Load in PostgreSQL 2.0
51mPostgreSQL: Practical Examples of SQL Query Optimization
47mPostgreSQL worst practices
45mMake Your SQL Queries 10,000x Faster, for Good
51mTypical application mistakes that lead to bloat in PostgreSQL
36mPostgreSQL worst practices
42mPostgres: stories that will scare you
01h 00mThe 10 Deadly PostgreSQL Sins