Skip to content

Commit 1e157e6

Browse files
Merge pull request #280846 from varun-dhawan/varund-jul
[PostgreSQL] updates PG16 MVU details
2 parents c05515a + aac9aec commit 1e157e6

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Major version upgrades in Azure Database for PostgreSQL - Flexible Server
33
description: Learn how to use Azure Database for PostgreSQL - Flexible Server to do in-place major version upgrades of PostgreSQL on a server.
44
author: varun-dhawan
55
ms.author: varundhawan
6-
ms.date: 7/12/2024
6+
ms.date: 7/15/2024
77
ms.service: postgresql
88
ms.subservice: flexible-server
99
ms.topic: conceptual
@@ -47,6 +47,8 @@ Here are some of the important considerations with in-place major version upgrad
4747

4848
- Azure Database for PostgreSQL Flexible Server takes snapshot of your database during an upgrade. The snapshot is taken before the upgrade starts. If the upgrade fails, the system will automatically restore your database to its state from the snapshot.
4949

50+
- [PostgreSQL 16 introduces role-based security](./concepts-security.md#postgresql-16-changes-with-role-based-security) measures. After a major version upgrade on Azure Database for PostgreSQL Flexible Server, the first user created on the server—who is granted the ADMIN option—will now have administrative privileges over other roles for essential maintenance operations.
51+
5052
## Post upgrade/migrate
5153

5254
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.

0 commit comments

Comments
 (0)