Skip to content

update: PG maintenance downtime with huge pages on #1043

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+8 −8
Open

update: PG maintenance downtime with huge pages on #1043

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a5e953
pg maintenance downtime
wojcik-dorota Sep 11, 2025
af0229f
feedback
wojcik-dorota Sep 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/platform/concepts/maintenance-window.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Service maintenance, updates and upgrades
title: Service maintenance, updates, and upgrades
sidebar_label: Service maintenance
---

import ConsoleLabel from "@site/src/components/ConsoleIcons"
Expand Down Expand Up @@ -35,16 +36,15 @@ See [Upgrade PostgreSQL to a major version][pg].

### MySQL, PostgreSQL and Caching updates

For **MySQL®**, **PostgreSQL®** and **Caching**, the maintenance
process usually lasts around several seconds. The downtime comes from old
master stopping itself in a controlled manner and new master executing
promotion sequence after this.
For **MySQL®**, **PostgreSQL®** and **Caching**, the maintenance process should take no
more than 15 seconds. The downtime comes from the old primary stopping itself in a
controlled manner and the new primary executing a promotion sequence after this.

Once the promotion is complete the old
master node starts forwarding requests to the new master node so the
primary node starts forwarding requests to the new primary node so the
service is accessible before DNS updates are propagated, though clients
that end up reconnecting to the old master node will see additional
disconnection once the old master is permanently retired.
that end up reconnecting to the old primary node will see additional
disconnection once the old primary is permanently retired.

### Apache Kafka and OpenSearch updates

Expand Down