Maintenance Windows and Updates
What you'll learn: How to control when and how your managed database gets patched and upgraded without catching you off guard.
Why Maintenance Matters
Your managed database needs updates—security patches, bug fixes, and engine version upgrades—just like your phone needs updates. But unlike your phone, a database serves live applications that users depend on. You can't afford unplanned downtime or surprise disruptions during peak hours.
Maintenance windows are scheduled time blocks when the cloud provider can perform these necessary updates. Think of it like scheduling a dentist appointment: you pick a time that works for you rather than having the dentist show up randomly at your door.
How It Works
When you create a managed database instance, you specify:
- Maintenance window: A weekly time slot (e.g., "Sundays 2:00–3:00 AM UTC") when updates can occur
- Auto minor version upgrade: Whether to automatically apply small patches (like 14.2 → 14.3) during maintenance windows
- Major version upgrades: Manual control over big jumps (like PostgreSQL 13 → 14)
The cloud provider queues pending patches and applies them only during your chosen window. If nothing needs updating that week, nothing happens—your database runs undisturbed.
Minimizing Disruption
Choose maintenance windows during your lowest-traffic periods. For e-commerce sites, that might be 3 AM on a Tuesday. For B2B apps, perhaps Sunday mornings.
Minor updates often require brief reboots (1–3 minutes). Major upgrades may take longer and require testing first, so you typically trigger them manually after validating compatibility.
Key Takeaway: Maintenance windows let you control when your database updates happen, ensuring patches occur during low-traffic periods rather than disrupting users during business hours.