Skip to content

Commit 4db915d

Browse files
committed
FSPG New regions add and other minor changes
1 parent 9947985 commit 4db915d

File tree

5 files changed

+15
-8
lines changed

5 files changed

+15
-8
lines changed

articles/postgresql/flexible-server/concepts-compare-single-server-flexible-server.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ The following table provides a list of high-level features and capabilities comp
3232
| Underlying O/S | Windows | Linux |
3333
| AZ selection for application colocation | No | Yes |
3434
| Built-in connection pooler | No | Yes (PgBouncer)|
35-
| Uptime SLA | [SLA](https://azure.microsoft.com/support/legal/sla/postgresql)| [SLA](https://azure.microsoft.com/support/legal/sla/postgresql) |
35+
| Uptime SLA | [99.99% SLA](https://azure.microsoft.com/support/legal/sla/postgresql)| [Up to 99.99% SLA](https://azure.microsoft.com/support/legal/sla/postgresql) |
3636
| **Connectivity** | | |
3737
| Username in connection string | `<user_name>@server_name`. For example, `pgadmusr@mypgServer` | Just username. For example, `pgadmusr` |
3838
| lc_collate | English_United States.1252 | en_US.utf8 |

articles/postgresql/flexible-server/concepts-high-availability.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ ms.date: 08/03/2022
1515

1616
Azure Database for PostgreSQL - Flexible Server offers high availability configurations with automatic failover capabilities. The high availability solution is designed to ensure that committed data is never lost because of failures and that the database won't be a single point of failure in your software architecture. When high availability is configured, flexible server automatically provisions and manages a standby replica. Write-ahead-logs (WAL) is streamed to the replica in **synchronous** mode using PostgreSQL streaming replication. There are two high availability architectural models:
1717

18-
* **Zone-redundant HA**: This option provides a complete isolation and redundancy of infrastructure across multiple availability zones within a region. It provides the highest level of availability, but it requires you to configure application redundancy across zones. Zone-redundant HA is preferred when you want protection from availability zone level failures and when latency across the availability zone is acceptable. Zone-redundant HA is available in a [subset of Azure regions](./overview.md#azure-regions) where the region supports multiple [availability zones](../../availability-zones/az-overview.md). See the uptime [SLA](https://azure.microsoft.com/support/legal/sla/postgresql) offered in this configuration.
18+
* **Zone-redundant HA**: This option provides a complete isolation and redundancy of infrastructure across multiple availability zones within a region. It provides the highest level of availability, but it requires you to configure application redundancy across zones. Zone-redundant HA is preferred when you want protection from availability zone level failures and when latency across the availability zone is acceptable. Zone-redundant HA is available in a [subset of Azure regions](./overview.md#azure-regions) where the region supports multiple [availability zones](../../availability-zones/az-overview.md). Uptime [SLA of 99.99%](https://azure.microsoft.com/support/legal/sla/postgresql) is offered in this configuration.
1919

20-
* **Same-zone HA**: This option is preferred for infrastructure redundancy with lower network latency because the primary and standby servers will be in the same availability zone. It provides high availability without the need to configure application redundancy across zones. Same-zone HA is preferred when you want to achieve the highest level of availability within a single availability zone with the lowest network latency. Same-zone HA is available in all [Azure regions](./overview.md#azure-regions) where you can deploy Flexible Server. See the uptime [SLA](https://azure.microsoft.com/support/legal/sla/postgresql) offered in this configuration.
20+
* **Same-zone HA**: This option is preferred for infrastructure redundancy with lower network latency because the primary and standby servers will be in the same availability zone. It provides high availability without the need to configure application redundancy across zones. Same-zone HA is preferred when you want to achieve the highest level of availability within a single availability zone with the lowest network latency. Same-zone HA is available in all [Azure regions](./overview.md#azure-regions) where you can deploy Flexible Server. Uptime [SLA of 99.95%](https://azure.microsoft.com/support/legal/sla/postgresql) offered in this configuration.
2121

2222
High availability configuration enables automatic failover capability with zero data loss during planned events such as user-initiated scale compute operation, and also during unplanned events such as underlying hardware and software faults, network failures, and availability zone failures.
2323

@@ -239,7 +239,7 @@ Flexible servers that are configured with high availability, log data is replica
239239

240240
## Availability for non-HA servers
241241

242-
For Flexible servers configured **without** high availability, the service still provides built-in availability, storage redundancy and resiliency to help to recover from any planned or unplanned downtime events. See the uptime [SLA](https://azure.microsoft.com/support/legal/sla/postgresql) offered in this configuration.
242+
For Flexible servers configured **without** high availability, the service still provides built-in availability, storage redundancy and resiliency to help to recover from any planned or unplanned downtime events. Uptime [SLA of 99.9%](https://azure.microsoft.com/support/legal/sla/postgresql) is offered in this non-HA configuration.
243243

244244
:::image type="content" source="./media/business-continuity/concepts-availability-without-zone-redundant-ha-architecture.png" alt-text="Diagram that shows availability without zone redundant ha - steady state." border="false" lightbox="./media/business-continuity/concepts-availability-without-zone-redundant-ha-architecture.png":::
245245

articles/postgresql/flexible-server/overview.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: sunilagarwal
66
ms.service: postgresql
77
ms.subservice: flexible-server
88
ms.topic: overview
9-
ms.date: 07/20/2022
9+
ms.date: 08/11/2022
1010
ms.custom: "mvc, references_regions"
1111
---
1212

@@ -104,6 +104,7 @@ One advantage of running your workload in Azure is global reach. The flexible se
104104
| East US | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
105105
| East US 2 | :heavy_check_mark: | :x: $ | :heavy_check_mark: |
106106
| France Central | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
107+
| France South | :heavy_check_mark: | :x: | :x: |
107108
| Germany West Central | :x: $$ | :x: $ | :x: |
108109
| Japan East | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
109110
| Japan West | :heavy_check_mark: | :x: | :heavy_check_mark: |
@@ -113,12 +114,14 @@ One advantage of running your workload in Azure is global reach. The flexible se
113114
| North Central US | :heavy_check_mark: | :x: | :heavy_check_mark: |
114115
| North Europe | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
115116
| Norway East | :heavy_check_mark: | :x: | :x: |
116-
| South Africa North | :heavy_check_mark: | :x: | :x: |
117+
| Qatar Central | :heavy_check_mark: | :x: | :x: |
118+
| South Africa North | :heavy_check_mark: | :heavy_check_mark: ** | :x: |
117119
| South Central US | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
118120
| South India | :x: $$ | :x: | :heavy_check_mark: |
119121
| Southeast Asia | :heavy_check_mark: | :x: $ | :heavy_check_mark: |
120122
| Sweden Central | :heavy_check_mark: | :x: | :x: |
121123
| Switzerland North | :heavy_check_mark: | :x: $ ** | :x: |
124+
| Switzerland West | :heavy_check_mark: | :x: | :x: |
122125
| UAE North | :heavy_check_mark: | :x: | :x: |
123126
| US Gov Arizona | :heavy_check_mark: | :x: | :x: |
124127
| US Gov Virginia | :heavy_check_mark: | :heavy_check_mark: | :x: |

articles/postgresql/flexible-server/release-notes.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.custom: references_regions
77
ms.service: postgresql
88
ms.subservice: flexible-server
99
ms.topic: overview
10-
ms.date: 06/29/2022
10+
ms.date: 08/11/2022
1111
---
1212

1313
# Release notes - Azure Database for PostgreSQL - Flexible Server
@@ -16,6 +16,10 @@ ms.date: 06/29/2022
1616

1717
This page provides latest news and updates regarding feature additions, engine versions support, extensions, and any other announcements relevant for Flexible Server - PostgreSQL.
1818

19+
## Release: August 2022
20+
21+
* Support for [new regions](overview.md#azure-regions) Qatar Central, Switzerland West, France South.
22+
1923
## Release: July 2022
2024

2125
* Support for [Geo-redundant backup](./concepts-backup-restore.md#geo-redundant-backup-and-restore-preview) in [additional regions](./overview.md#azure-regions) - Australia East, Australia Southeast, Canada Central, Canada East, UK South, UK West, East US, West US, East Asia, Southeast Asia, North Central US, South Central US, and France Central.

articles/postgresql/single-server/overview-postgres-choose-server-options.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The main differences between these options are listed in the following table:
2727

2828
| **Attribute** | **Postgres on Azure VMs** | **PostgreSQL as PaaS** |
2929
| ----- | ----- | ----- |
30-
| **Availability SLA** |- [Virtual Machine SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines/v1_9/) | - [Single Server, Flexible Server, and Hyperscale (Citus) SLA](https://azure.microsoft.com/support/legal/sla/postgresql/v1_2/)|
30+
| **Availability SLA** |- [Virtual Machine SLA](https://azure.microsoft.com/support/legal/sla/virtual-machines) | - [Single Server, Flexible Server, and Hyperscale (Citus) SLA](https://azure.microsoft.com/support/legal/sla/postgresql)|
3131
| **OS and PostgreSQL patching** | - Customer managed | - Single Server – Automatic <br> - Flexible Server – Automatic with optional customer managed window <br> - Hyperscale (Citus) – Automatic |
3232
| **High availability** | - Customers architect, implement, test, and maintain high availability. Capabilities might include clustering, replication etc. | - Single Server: built-in <br> - Flexible Server: built-in <br> - Hyperscale (Citus): built with standby |
3333
| **Zone Redundancy** | - Azure VMs can be set up to run in different availability zones. For an on-premises solution, customers must create, manage, and maintain their own secondary data center. | - Single Server: No <br> - Flexible Server: Yes <br> - Hyperscale (Citus): No |

0 commit comments

Comments
 (0)