You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/postgresql/flexible-server/overview.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,11 +34,11 @@ Azure Database for PostgreSQL - Flexible Server is a fully managed database serv
34
34
35
35
:::image type="content" source="./media/overview/overview-flexible-server.png" alt-text="Diagram of Flexible Server - Overview." lightbox="./media/overview/overview-flexible-server.png":::
36
36
37
-
Flexible servers are best suited for
37
+
Flexible servers are best suited for:
38
38
39
39
- Application developments requiring better control and customizations.
40
-
- Zone redundant high availability
41
-
- Managed maintenance windows
40
+
- Zone redundant high availability.
41
+
- Managed maintenance windows.
42
42
43
43
## Architecture and high availability
44
44
@@ -135,7 +135,7 @@ $ New Zone-redundant high availability deployments are temporarily blocked in th
135
135
136
136
$$ New server deployments are temporarily blocked in these regions. Already provisioned servers are fully supported.
137
137
138
-
** Zone-redundant high availability can now be deployed when you provision new servers in these regions. Any existing servers deployed in AZ with *no preference* (which you can check on the Azure portal) before the region started to support AZ, even when you enable zone-redundant HA, the standby is provisioned in the same AZ (same-zone HA) as the primary server. To enable zone-redundant high availability, [follow the steps.](how-to-manage-high-availability-portal.md#enabling-zone-redundant-ha-after-the-region-supports-az).
138
+
** Zone-redundant high availability can now be deployed when you provision new servers in these regions. Any existing servers deployed in AZ with *no preference* (which you can check on the Azure portal) before the region started to support AZ, even when you enable zone-redundant HA, the standby is provisioned in the same AZ (same-zone HA) as the primary server. To enable zone-redundant high availability, [follow the steps](how-to-manage-high-availability-portal.md#enabling-zone-redundant-ha-after-the-region-supports-az).
139
139
140
140
<!-- We continue to add more regions for flexible servers. -->
141
141
> [!NOTE]
@@ -157,7 +157,7 @@ We continue to support Single Server and encourage you to adopt Flexible Server
157
157
158
158
### What is Microsoft's policy to address PostgreSQL engine defects?
159
159
160
-
Refer to Microsoft's current policy [here](../../postgresql/flexible-server/concepts-supported-versions.md#managing-postgresql-engine-defects)
160
+
Refer to Microsoft's current policy [here](../../postgresql/flexible-server/concepts-supported-versions.md#managing-postgresql-engine-defects).
161
161
162
162
## Contacts
163
163
@@ -174,4 +174,4 @@ In addition, consider the following points of contact as appropriate:
174
174
175
175
## Next steps
176
176
177
-
Now that you've read an introduction to Azure Database for PostgreSQL flexible server deployment mode, you're ready to create your first server: [Create an Azure Database for PostgreSQL - Flexible Server using Azure portal](./quickstart-create-server-portal.md)
177
+
Now that you've read an introduction to Azure Database for PostgreSQL flexible server deployment mode, you're ready to create your first server: [Create an Azure Database for PostgreSQL - Flexible Server using Azure portal](./quickstart-create-server-portal.md).
0 commit comments