Merge pull request #280655 from varun-dhawan/varund-jul

[PostgreSQL] updated the MVU docs fail condition

Author: prmerger-automator[bot]

articles/postgresql/flexible-server/concepts-major-version-upgrade.md

@@ -3,12 +3,10 @@ title: Major version upgrades in Azure Database for PostgreSQL - Flexible Server
 description: Learn how to use Azure Database for PostgreSQL - Flexible Server to do in-place major version upgrades of PostgreSQL on a server.
 author: varun-dhawan
 ms.author: varundhawan
-ms.date: 7/8/2024
+ms.date: 7/11/2024
 ms.service: postgresql
 ms.subservice: flexible-server
 ms.topic: conceptual
-ms.custom:
-  - references_regions
 ---
 
 # Major version upgrades in Azure Database for PostgreSQL - Flexible Server
@@ -47,6 +45,8 @@ Here are some of the important considerations with in-place major version upgrad
 
 - After an in-place major version upgrade is successful, there are no automated ways to revert to the earlier version. However, you can perform a point-in-time recovery (PITR) to a time before the upgrade to restore the previous version of the database instance.
 
+- Azure Database for PostgreSQL Flexible Server takes two snapshots of your database during an upgrade. The first snapshot is taken before the upgrade starts, and the second snapshot is taken after the upgrade finishes. If the upgrade fails, the system will automatically restore your database to its state from the first snapshot.
+
 ## Post upgrade/migrate
 
 After the major version upgrade is complete, we recommend to run the `ANALYZE` command  in each database to refresh the `pg_statistic` table. Otherwise, you may run into performance issues.