PostgreSQL: Ups, DevOps...
summary
Explains practical limits of automating PostgreSQL ops: use Ansible or Chef/Puppet/Salt for OS/config distro and repetitive tasks, but keep human review for monitoring, index rebuilds and schema changes; automations cut errors and scale from tens to hundreds of VMs yet cause failures when untested—examples: regex template bug that generated invalid configs, accidental mass reboot from clipboard paste, long ALTER TABLE deadlocking writers, and a failed major upgrade that deleted the old data directory. Recommends test environments, runbooks and on‑call rotation.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 4:04Admin tasks classification
- 12:34Automation problems and solutions
- 20:00Automation tools
- 27:54Pitfalls from practice
- 34:04Lessons and recommendations
related talks
55mManaging PostgreSQL With Ansible
36mUnlocking the Benefits of Database DevOps and Automation
01h 39mPostOps: A Non-Surgical Tale of Software, Fragility, and Reliability
30mManaging Postgres at scale: Challenges, Tools & Techniques
52mManaging PostgreSQL changes for the Agile DBA
17mEmpowering Engineers With a Database DevOps Strategy
35mAnswering the Big Question About Chef, Postgres and All That
34mDo we really need a DBA to manage our PostgreSQL databases on DBaaS