Leveraging pgBadger for Effective PostgreSQL Troubleshooting
summary
pgBadger parses PostgreSQL text logs into a single HTML report that lists counts of ANALYZE/VACUUM, tables affected and rows/pages removed, distribution and sizes of temporary files and the queries that create them, lock types and waiting queries (it cannot show which query holds a lock). Common, actionable findings: temp files average size flags low work_mem; autovacuum focusing on one tiny table is solved by per-table settings (e.g. autovacuum_vacuum_threshold=10000, scale factor=0); requires logging_collector and set log_line_prefix; supports multi-file parsing, -j parallelism, RDS and Azure Flex formats.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:14About Alicja
- 2:30What is pgBadger
- 4:00Troubleshooting checklist
- 6:24pgBadger
- 7:35Installation
- 8:08pgBadger Configuration
- 12:56Demo
- 16:50Sample Report
- 28:22Events
- 31:43Developer Errors
- 34:03Locked Queries
- 36:05Loline Prefix
- 38:57Questions
related talks
47mIdentifying Slow Queries and Fixing Them!
50mPostgreSQL Query Performance Insights
57mQuery Logging and Workload Analysis
27mMaintaining Large Tables in PostgreSQL
26mTroubleshooting High CPU Utilization in PostgreSQL Databases
39mDeep dive into PostgreSQL internal statistics
25mUnderstanding & Managing Postgres Table Bloat
27mPostgres Performance in 15 Minutes