Debugging Databases for Developers
summary
A practical checklist for troubleshooting PostgreSQL for developers: inspect PostgreSQL logs (set log_line_prefix and log_min_duration_statement), verify connectivity with psql (check listen_addresses, pg_hba.conf, role LOGIN and reload config), confirm server process/state (systemctl or pg_ctl), check disk space and WAL/archive_command before deleting WAL files, enable pg_stat_statements to find expensive queries, and if a table is lost restore the backup to another host and extract rows with pg_dump/pg_restore instead of overwriting the cluster.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:03Where to find info
- 10:36Connection problems
- 21:27PostgreSQL won't start
- 24:01Disk space shortage
- 32:11Slow queries
- 41:29Missing object
- 43:17Safe practice
related talks
20mDebugging Data Corruption in PostgreSQL
46mPostgres for the SQL Server DBA
32mDebugging Data Corruption in PostgreSQL: A Systematic Approach
49mHow to Ride Elephants Safely: Working with PostgreSQL when your DBA is not around
53mTop Development Mistakes When Working with PostgreSQL
47mBeginner's guide to PostgreSQL Hacking
49mHELP!!1! The database is slow!!
52mHow Not to 'Sleep Through' Problems in Postgres Databases