Lesson 11 of 12 · Incidents and project
Production incidents: full disk, blocking lock, lagging autovacuum, saturated connections
Objective
Know what to do, in order, when the production database stops at 3 a.m.: identify the cause from the logs and system views, apply the move that restores service without loss, then fix it for good.
This lesson is part of the full course
Unlock Database administration: MariaDB, MySQL and PostgreSQL in production to read every lesson, do the exercises, access the simulations and earn your certificate.
Already enrolled? Log in.