Merge pull request #938 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 12/2
MicrosoftDocs · Dec 2, 2024 · 2687647 · 2687647
2 parents 7c19d63 + 12acd11
commit 2687647
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 0 deletions.
diff --git a/...ervice/includes/iaas/prerequisites-migration-service-postgresql-offline-iaas.md b/...ervice/includes/iaas/prerequisites-migration-service-postgresql-offline-iaas.md
@@ -31,6 +31,8 @@ Before you begin the migration, you must set up an [Azure Database for PostgreSQ
 
 The SKU chosen for the Azure Database for PostgreSQL should correspond with the specifications of the source database to ensure compatibility and adequate performance.
 
+When migrating across PostgreSQL versions (major or minor), ensure compatibility between your database and application by reviewing the [release notes](https://www.postgresql.org/docs/17/release.html) for potential breaking changes.
+
 ### Configure network setup
 
 Network setup is crucial for the migration service to function correctly. Ensure that the source PostgreSQL server can communicate with the target Azure Database for PostgreSQL server. The following network configurations are essential for a successful migration.

diff --git a/...service/includes/iaas/prerequisites-migration-service-postgresql-online-iaas.md b/...service/includes/iaas/prerequisites-migration-service-postgresql-online-iaas.md
@@ -37,6 +37,7 @@ If the source PostgreSQL version is less than 9.5, upgrade it to 9.5 or higher b
 - Before migrating, Azure Database for PostgreSQL – Flexible server must be created.
 - SKU provisioned for Azure Database for PostgreSQL – Flexible server should match with the source.
 - To create a new Azure Database for PostgreSQL, visit [Create an Azure Database for PostgreSQL](../../../../flexible-server/quickstart-create-server-portal.md)
+- When migrating across PostgreSQL versions (major or minor), ensure compatibility between your database and application by reviewing the [release notes](https://www.postgresql.org/docs/17/release.html) for potential breaking changes.
 
 ### Enable CDC as a source
 

diff --git a/...erequisites/prerequisites-migration-service-postgresql-offline-single-server.md b/...erequisites/prerequisites-migration-service-postgresql-offline-single-server.md
@@ -25,6 +25,8 @@ Source PostgreSQL version should be `>= 9.5`. If the source PostgreSQL version i
 
 - For detailed instructions on creating a new Azure Database for PostgreSQL, refer to the following link: [Quickstart: Create server](/azure/postgresql/flexible-server/).
 
+- When migrating across PostgreSQL versions (major or minor), ensure compatibility between your database and application by reviewing the [release notes](https://www.postgresql.org/docs/17/release.html) for potential breaking changes.
+
 ### Network setup
 
 Network setup is crucial for the migration service to function correctly. Ensure that the source PostgreSQL server can communicate with the target Azure Database for PostgreSQL server. The following network configurations are essential for a successful migration.

diff --git a/...rerequisites/prerequisites-migration-service-postgresql-online-single-server.md b/...rerequisites/prerequisites-migration-service-postgresql-online-single-server.md
@@ -44,6 +44,7 @@ To prevent the Online migration from running out of storage to store the logs, e
 
 - ALTER SYSTEM SET max_replication_slots = `number of databases to migrate` + 1;
 
+- When migrating across PostgreSQL versions (major or minor), ensure compatibility between your database and application by reviewing the [release notes](https://www.postgresql.org/docs/17/release.html) for potential breaking changes.
 
 > [!IMPORTANT]  
 > [Change the **password_encryption** server parameter on your flexible server](../../../../flexible-server/how-to-configure-server-parameters-using-portal.md) from SCRAM-SHA-256 to MD5 before initating the migration. This is essential for the existing credentials on single server to work on your flexible server.