Merge pull request #238353 from kabharati/patch-75

Update how-to-upgrade-using-dump-and-restore.md

Author: v-regandowner

articles/postgresql/single-server/how-to-upgrade-using-dump-and-restore.md

@@ -21,6 +21,7 @@ ms.date: 06/24/2022
 You can upgrade your PostgreSQL server deployed in Azure Database for PostgreSQL by migrating your databases to a higher major version server using following methods.
 * **Offline** method using PostgreSQL [pg_dump](https://www.postgresql.org/docs/current/static/app-pgdump.html) and [pg_restore](https://www.postgresql.org/docs/current/static/app-pgrestore.html) which incurs downtime for migrating the data. This document addresses this method of upgrade/migration.
 * **Online** method using [Database Migration Service](../../dms/tutorial-azure-postgresql-to-azure-postgresql-online-portal.md) (DMS). This method provides a reduced downtime migration and keeps the target database in-sync with the source and you can choose when to cut-over. However, there are few prerequisites and restrictions to be addressed for using DMS. For details, see the [DMS documentation](../../dms/tutorial-azure-postgresql-to-azure-postgresql-online-portal.md).
+* **In-place Major Version Upgrade** method using [Azure Database for PostgreSQL - Flexible Server](../flexible-server/how-to-perform-major-version-upgrade-portal.md).In-place major version upgrade feature performs major version upgrade of the server with just a click. This simplifies the upgrade process minimizing the disruption to users and applications accessing the server. In-place upgrades are a simpler way to upgrade the major version of the instance, as they retain the server name and other settings of the current server after the upgrade, and don't require data migration or changes to the application connection strings. In-place upgrades are faster and involve shorter downtime than data migration.
 
 The following table provides some recommendations based on database sizes and scenarios.