Skip to content

Commit b738d9e

Browse files
authored
Merge pull request #1 from jan-eng/patch-1
fixed build break
2 parents 05bb044 + f879d9a commit b738d9e

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/postgresql/concepts-pricing-tiers.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,8 @@ The service automatically takes backups of your server. The minimum retention pe
9696

9797
After you create your server, you can independently change the vCores, the hardware generation, the pricing tier (except to and from Basic), the amount of storage, and the backup retention period. You can't change the backup storage type after a server is created. The number of vCores can be scaled up or down. The backup retention period can be scaled up or down from 7 to 35 days. The storage size can only be increased. Scaling of the resources can be done either through the portal or Azure CLI. For an example of scaling by using Azure CLI, see [Monitor and scale an Azure Database for PostgreSQL server by using Azure CLI](scripts/sample-scale-server-up-or-down.md).
9898

99-
> [!NOTE] The storage size can only be increased, and there is no option to revert back after completion of this task.
99+
> [!NOTE]
100+
> The storage size can only be increased. You cannot go back to a smaller storage size after the increase.
100101
101102
When you change the number of vCores, the hardware generation, or the pricing tier, a copy of the original server is created with the new compute allocation. After the new server is up and running, connections are switched over to the new server. During the moment when the system switches over to the new server, no new connections can be established, and all uncommitted transactions are rolled back. This window varies, but in most cases, is less than a minute.
102103

0 commit comments

Comments
 (0)