Maintenance and versions

Plexivo keeps your databases and caches patched for you. You choose when updates happen, you hear about them well ahead, and you can apply them early or, within limits, later.

Your maintenance window#

Each Plexivo Postgres, Plexivo MySQL and Plexivo Cache resource has a weekly window, in your organisation’s own time. The Maintenance card on the resource’s Overview shows the window, the next update and what it means for your app, the version and any freeze. Choose Edit window to pick the Day, the start time (every half hour) and the Length: 1, 2, 3, 4, 6 or 8 hours. Choose Save window. Anything already scheduled moves into the new window.

Until you choose, the window is Sunday 02:30–03:30 in your organisation’s time (India Standard Time for India).

Updates arrive lets you choose First, as soon as an update’s notice ends, or A week later. A week later suits a production database that follows a test copy. A critical security fix reaches everyone at once.

Freeze periods#

Busy season coming? Choose Freeze on the Maintenance card and add the first and last day. No planned maintenance starts on those days, and anything scheduled moves to your first window after them.

A critical security fix still applies in your window during a freeze, and an update you start yourself runs when you ask.

Notice#

Plexivo emails your owners and admins when an update is scheduled, a week before it and the day before. By default, updates are announced:

The first notice of every update, and every email about a security update, is always sent. The reminders and the “done” email of routine updates can be turned off with Maintenance reminders in Settings → Notifications, or Emails on the Maintenance card. Maintenance counts as announced only when the email reached every owner and admin. By default, maintenance announced at least five days ahead does not count against the SLA while it stays inside its window, for up to four hours. Your organisation’s Activity also lists each update when it is scheduled and when it is done.

Apply now, move or postpone#

The Scheduled list on the Maintenance tab shows each update, when it will run, what it means for your app and the latest you can postpone it to.

• Apply now starts the update within a minute or two.
• Next window brings it forward to your next window.
• Postpone a week moves it to your window at least seven days later, up to its limit.

Through the API you can also pick an exact time up to the update’s deadline: POST /api/v1/tenants/{tenant}/deployments/{id}/maintenance/{update}/reschedule with {"at": "2026-11-08T22:00:00+05:30"}, or {"to": "next_window"}.

An update whose window passes without it starting, for example while the resource is stopped, moves to your next window and you are reminded again.

What happens during an update#

• A database with a standby is updated standby first, then switches over to the updated standby: about 7 seconds of reconnects for Plexivo Postgres and about 14 for Plexivo MySQL, as measured.
• A single-instance Plexivo Postgres restarts once: about 72 seconds of reconnects, as measured.
• A single-instance Plexivo MySQL or a Plexivo Cache restarts once; clients reconnect when it is back.
• Backups keep running.
• If an update is not healthy within 45 minutes, Plexivo puts the previous version back automatically and tells you.

Plexivo App Runner apps and Plexivo Kubernetes workloads have no maintenance window. Plexivo patches the machines under them one at a time, so an app with two or more instances keeps serving; one with a single instance is restarted on another machine.

Major version upgrades#

Moving Plexivo Postgres from 17 to 18 is your decision, made when you are ready.

1. Check. Plexivo runs pre-upgrade checks, such as extensions, replication slots, disk space and backups, and tells you anything to fix first.
2. Choose when. Now, or in your maintenance window. Type the database’s name to confirm.
3. Upgrade. Plexivo takes a backup, upgrades, checks the result and takes another backup. The database is offline while the upgrade itself runs.

If the upgrade fails, the database comes back on its old version, unchanged. You can cancel a scheduled upgrade until it starts. After a successful upgrade, the way back is the backup taken before it, restored into a new database.

Supported versions#

Plexivo MySQL and Plexivo Cache each run one major version and receive patch updates. The console marks a version that reaches the end of support within six months.