From 92df4df0c662a91995d97c3f3d11ed461c1d8b0f Mon Sep 17 00:00:00 2001 From: Firdevs ARSLAN Date: Wed, 15 Jul 2026 15:41:42 +0200 Subject: [PATCH 1/4] docs(mongodb): added upgrade version --- ...ion.mdx => postgresql-upgrade-version.mdx} | 2 +- .../menu.ts | 4 +- .../how-to/mongodb-upgrade-engine-version.mdx | 64 +++++++++++++++++++ pages/managed-mongodb-databases/menu.ts | 4 ++ 4 files changed, 71 insertions(+), 3 deletions(-) rename pages/managed-databases-for-postgresql-and-mysql/how-to/{upgrade-version.mdx => postgresql-upgrade-version.mdx} (98%) create mode 100644 pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/postgresql-upgrade-version.mdx similarity index 98% rename from pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx rename to pages/managed-databases-for-postgresql-and-mysql/how-to/postgresql-upgrade-version.mdx index 86fce7fb64..0be84eae16 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/postgresql-upgrade-version.mdx @@ -1,5 +1,5 @@ --- -title: How to upgrade your Database Instance engine version +title: Upgrade your PostgreSQL and MySQL Database Instance engine version description: Instructions for upgrading the version of your PostgreSQL or MySQL database engine. tags: managed-database postgresql mysql engine version database engine dates: diff --git a/pages/managed-databases-for-postgresql-and-mysql/menu.ts b/pages/managed-databases-for-postgresql-and-mysql/menu.ts index f8305a36e3..a24d7fc354 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/menu.ts +++ b/pages/managed-databases-for-postgresql-and-mysql/menu.ts @@ -75,8 +75,8 @@ export const managedDatabasesForPostgresqlAndMysqlMenu = { slug: 'monitor-databases-cockpit', }, { - label: 'Upgrade Database Instance engine versions', - slug: 'upgrade-version', + label: 'Upgrade PostgreSQL and MySQL Database Instance engine versions', + slug: 'postgresql-upgrade-version', }, { label: 'Apply scheduled maintenance', diff --git a/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx b/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx new file mode 100644 index 0000000000..342aaade64 --- /dev/null +++ b/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx @@ -0,0 +1,64 @@ +--- +title: Upgrade your MongoDB Database Instance engine version +description: Instructions for upgrading the version of your MongoDB database engine. +tags: managed-database mongodb engine version database engine +dates: + validation: 2025-07-15 + posted: 2023-02-27 +--- +import Requirements from '@macros/iam/requirements.mdx' + +If your database engine is outdated, you can upgrade the version to the latest one anytime via the Scaleway console. + +You must upgrade your engine version if your Database Instance uses an End of Life engine version that is no longer maintained. + + +The version upgrade is only available for Database Instances using engine versions preceding the most recent version available. + + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [MongoDB Database Instance](/managed-mongodb-databases/how-to/create-a-database-instance/) running on an outdated engine version + +## How to remove incompatible data types + +Before upgrading to a newer major PostgreSQL version, you must remove any data types incompatible with the `pg_upgrade` tool. + +The `reg*` data type, for example, cannot be persisted by `pg_upgrade`. + +Run the following command in your Database Instance to identify all instances of the `reg*` data type: + +```sql +SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalog.pg_attribute a + WHERE c.oid = a.attrelid + AND NOT a.attisdropped + AND a.atttypid IN ('pg_catalog.regproc'::pg_catalog.regtype, + 'pg_catalog.regprocedure'::pg_catalog.regtype, + 'pg_catalog.regoper'::pg_catalog.regtype, + 'pg_catalog.regoperator'::pg_catalog.regtype, + 'pg_catalog.regconfig'::pg_catalog.regtype, + 'pg_catalog.regdictionary'::pg_catalog.regtype) + AND c.relnamespace = n.oid + AND n.nspname NOT IN ('pg_catalog', 'information_schema');  +``` + +We recommend you remove the identified instances before continuing. + +## How to upgrade the engine version + +1. Under **Databases** on the side menu, click **MongoDB**. A list of your Database Instances appears. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the name of the database whose engine you want to upgrade. The Database Instance information page appears. +4. Under **Database engine**, click **Upgrade**. A pop-up appears. +5. Select the new version to which you want to upgrade.
+ The upgrade will create a new instance with a public endpoint by default. The client will need to configure new endpoints on the new instance and redirect their application to these new endpoints. + + + When you upgrade to a new version: + - There is no synchronization between the source and target Database Instances. To avoid data loss, we recommend you stop all write operations on your applications during the upgrade. If you let them run during the process, data will only be stored in the source Database Instance. + + +6. Click **Upgrade version**. A new Database Instance is created. + diff --git a/pages/managed-mongodb-databases/menu.ts b/pages/managed-mongodb-databases/menu.ts index 661012e59e..a22769348c 100644 --- a/pages/managed-mongodb-databases/menu.ts +++ b/pages/managed-mongodb-databases/menu.ts @@ -42,6 +42,10 @@ export const managedMongodbDatabasesMenu = { label: 'Increase the storage size', slug: 'increase-volume', }, + { + label: 'Upgrade MongoDB Database Instance engine versions', + slug: 'mongodb-upgrade-engine-version', + }, { label: 'Delete a Database Instance', slug: 'delete-a-database-instance', From 05ac614280159ecebeb57174f4ba0a9824f34af0 Mon Sep 17 00:00:00 2001 From: Firdevs ARSLAN Date: Wed, 15 Jul 2026 16:02:13 +0200 Subject: [PATCH 2/4] removed section --- .../how-to/mongodb-upgrade-engine-version.mdx | 24 ------------------- 1 file changed, 24 deletions(-) diff --git a/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx b/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx index 342aaade64..2f39db184c 100644 --- a/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx +++ b/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx @@ -22,30 +22,6 @@ The version upgrade is only available for Database Instances using engine versio - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [MongoDB Database Instance](/managed-mongodb-databases/how-to/create-a-database-instance/) running on an outdated engine version -## How to remove incompatible data types - -Before upgrading to a newer major PostgreSQL version, you must remove any data types incompatible with the `pg_upgrade` tool. - -The `reg*` data type, for example, cannot be persisted by `pg_upgrade`. - -Run the following command in your Database Instance to identify all instances of the `reg*` data type: - -```sql -SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalog.pg_attribute a - WHERE c.oid = a.attrelid - AND NOT a.attisdropped - AND a.atttypid IN ('pg_catalog.regproc'::pg_catalog.regtype, - 'pg_catalog.regprocedure'::pg_catalog.regtype, - 'pg_catalog.regoper'::pg_catalog.regtype, - 'pg_catalog.regoperator'::pg_catalog.regtype, - 'pg_catalog.regconfig'::pg_catalog.regtype, - 'pg_catalog.regdictionary'::pg_catalog.regtype) - AND c.relnamespace = n.oid - AND n.nspname NOT IN ('pg_catalog', 'information_schema');  -``` - -We recommend you remove the identified instances before continuing. - ## How to upgrade the engine version 1. Under **Databases** on the side menu, click **MongoDB**. A list of your Database Instances appears. From 21752f11c337a9fe30af6f20244eee73be1b5400 Mon Sep 17 00:00:00 2001 From: Firdevs ARSLAN Date: Wed, 15 Jul 2026 16:03:12 +0200 Subject: [PATCH 3/4] removed title --- .../how-to/mongodb-upgrade-engine-version.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx b/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx index 2f39db184c..f5643e1bdf 100644 --- a/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx +++ b/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx @@ -22,8 +22,6 @@ The version upgrade is only available for Database Instances using engine versio - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [MongoDB Database Instance](/managed-mongodb-databases/how-to/create-a-database-instance/) running on an outdated engine version -## How to upgrade the engine version - 1. Under **Databases** on the side menu, click **MongoDB**. A list of your Database Instances appears. 2. Select the geographical region of the Instance you want to manage from the drop-down. 3. Click the name of the database whose engine you want to upgrade. The Database Instance information page appears. From 9b3091783e3bcc17bf06f8aea7448b32d45fe191 Mon Sep 17 00:00:00 2001 From: Firdevs ARSLAN Date: Wed, 15 Jul 2026 17:20:17 +0200 Subject: [PATCH 4/4] typos --- .../how-to/mongodb-upgrade-engine-version.mdx | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx b/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx index f5643e1bdf..53b108522f 100644 --- a/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx +++ b/pages/managed-mongodb-databases/how-to/mongodb-upgrade-engine-version.mdx @@ -3,8 +3,8 @@ title: Upgrade your MongoDB Database Instance engine version description: Instructions for upgrading the version of your MongoDB database engine. tags: managed-database mongodb engine version database engine dates: - validation: 2025-07-15 - posted: 2023-02-27 + validation: 2026-07-15 + posted: 2026-07-15 --- import Requirements from '@macros/iam/requirements.mdx' @@ -27,11 +27,10 @@ The version upgrade is only available for Database Instances using engine versio 3. Click the name of the database whose engine you want to upgrade. The Database Instance information page appears. 4. Under **Database engine**, click **Upgrade**. A pop-up appears. 5. Select the new version to which you want to upgrade.
- The upgrade will create a new instance with a public endpoint by default. The client will need to configure new endpoints on the new instance and redirect their application to these new endpoints. + The upgrade will create a new Instance with a public endpoint by default. The client will need to configure new endpoints on the new Instance and redirect their application to these new endpoints. - When you upgrade to a new version: - - There is no synchronization between the source and target Database Instances. To avoid data loss, we recommend you stop all write operations on your applications during the upgrade. If you let them run during the process, data will only be stored in the source Database Instance. + When you upgrade to a new version, there is no synchronization between the source and target Database Instances. To avoid data loss, we recommend you stop all write operations on your applications during the upgrade. If you let them run during the process, data will only be stored in the source Database Instance. 6. Click **Upgrade version**. A new Database Instance is created.