Azure Database for PostgreSQL - Flexible Server
APPLIES TO: 
Azure Database for PostgreSQL - Flexible Server
Azure Database for PostgreSQL powered by the PostgreSQL community edition is available in two deployment modes:
This article provides an overview and introduction to the core concepts of the Azure Database for PostgreSQL flexible server deployment model. Whether you're just starting out or looking to refresh your knowledge, this introductory video offers a comprehensive overview of Azure Database for PostgreSQL flexible server, helping you get acquainted with its key features and capabilities.
Overview
Azure Database for PostgreSQL flexible server is a fully managed database service designed to provide more granular control and flexibility over database management functions and configuration settings. The service generally provides more flexibility and server configuration customizations based on user requirements. The flexible server architecture allows users to collocate the database engine with the client tier for lower latency and choose high availability within a single availability zone and across multiple availability zones. Azure Database for PostgreSQL flexible server instances also provide better cost optimization controls with the ability to stop/start your server and a burstable compute tier ideal for workloads that don't need full compute capacity continuously. The service supports the community version of PostgreSQL 11, 12, 13, 14, 15 and 16. The service is available in various Azure regions.
Azure Database for PostgreSQL flexible server instances are best suited for
- Application developments requiring better control and customizations.
- Zone redundant high availability.
- Managed maintenance windows.
Architecture and high availability
The Azure Database for PostgreSQL flexible server deployment model is designed to support high availability within a single availability zone and across multiple availability zones. The architecture separates compute and storage. The database engine runs on a container inside a Linux virtual machine, while data files reside on Azure storage. The storage maintains three locally redundant synchronous copies of the database files ensuring data durability.
If zone redundant high availability is configured, the service provisions and maintains a warm standby server across the availability zone within the same Azure region. The data changes on the source server are synchronously replicated to the standby server to ensure zero data loss. With zone redundant high availability, once the planned or unplanned failover event is triggered, the standby server comes online immediately and is available to process incoming transactions. This allows the service resiliency from availability zone failure within an Azure region that supports multiple availability zones, as shown in the picture below.
See High availability for more details.
Automated patching with a managed maintenance window
The service performs automated patching of the underlying hardware, OS, and database engine. The patching includes security and software updates. For the PostgreSQL engine, minor version upgrades are included in the planned maintenance release. Users can configure the patching schedule to be system managed or define their custom schedule. During the maintenance schedule, the patch is applied, and the server may need to be restarted as part of the patching process to complete the update. With the custom schedule, users can make their patching cycle predictable and choose a maintenance window with minimum impact on the business. Generally, the service follows a monthly release schedule as part of the continuous integration and release.
Automatic backups
Azure Database for PostgreSQL flexible server automatically creates server backups and stores them on the region's zone redundant storage (ZRS). Backups can restore your server to any point within the backup retention period. The default backup retention period is seven days. The retention can be optionally configured for up to 35 days. All backups are encrypted using AES 256-bit encryption. See Backups for more details.
Adjust performance and scale within seconds
Azure Database for PostgreSQL flexible server is available in three compute tiers: Burstable, General Purpose, and Memory Optimized. The Burstable tier is best suited for low-cost development and low concurrency workloads without continuous compute capacity. The General Purpose and Memory Optimized are better suited for production workloads requiring high concurrency, scale, and predictable performance. You can build your first application on a small database for a few dollars a month and then seamlessly adjust the scale to meet the needs of your solution.
Stop/Start server to lower TCO
Azure Database for PostgreSQL flexible server allows you to stop and start the server on-demand to lower your TCO. The compute tier billing is stopped immediately when the server is stopped. This can allow significant cost savings during development, testing, and time-bound predictable production workloads. The server remains stopped for seven days unless restarted sooner.
Enterprise-grade security
Azure Database for PostgreSQL flexible server uses the FIPS 140-2 validated cryptographic module for storage encryption of data at rest. Data are encrypted, including backups and temporary files created while running queries. The service uses the AES 256-bit cipher included in Azure storage encryption, and the keys can be system-managed (default). Azure Database for PostgreSQL flexible server encrypts data in motion with transport layer security (SSL/TLS) enforced by default. The service enforces and supports TLS version 1.2 only.
Azure Database for PostgreSQL flexible server instances allow full private access to the servers using Azure virtual network (VNet integration). Servers in the Azure virtual network can only be reached and connected through private IP addresses. With VNet integration, public access is denied, and servers can't be reached using public endpoints.
Monitor and alerting
Azure Database for PostgreSQL flexible server is equipped with built-in performance monitoring and alerting features. All Azure metrics have a one-minute frequency, each providing 30 days of history. You can configure alerts on the metrics. The service exposes host server metrics to monitor resource utilization and allows configuring slow query logs. Using these tools, you can quickly optimize your workloads and configure your server for the best performance.
Built-in PgBouncer
An Azure Database for PostgreSQL flexible server instance has a built-in PgBouncer, a connection pooler. You can enable it and connect your applications to your Azure Database for PostgreSQL flexible server instance via PgBouncer using the same hostname and port 6432.
Azure regions
One advantage of running your workload in Azure is global reach. Azure Database for PostgreSQL flexible server is currently available in the following Azure regions:
| Region | Intel V3/V4/V5/AMD Compute | Zone-Redundant HA | Same-Zone HA | Geo-Redundant backup |
|---|---|---|---|---|
| Australia Central | ✔️ (v3/v4 only) | ✔️ | ✔️ | ✔️ |
| Australia Central 2 * | ✔️ (v3/v4 only) | ✔️ | ✔️ | ✔️ |
| Australia East | ✔️ | ✔️ | ✔️ | ✔️ |
| Australia Southeast | ✔️ (v3/v4/v5 only) | ❌ | ✔️ | ✔️ |
| Brazil South | ✔️ (v3 only) | ❌ $ | ✔️ | ❌ |
| Brazil Southeast * | ✔️ (v3 only) | ❌ $ | ✔️ | ❌ |
| Canada Central | ✔️ | ✔️ | ✔️ | ✔️ |
| Canada East | ✔️ | ❌ | ✔️ | ✔️ |
| Central India | ✔️ | ✔️ | ✔️ | ✔️ |
| Central US | ✔️ (v3/v4 only) | ✔️ | ✔️ | ✔️ |
| China East 3 | ✔️ (v3/v4 only) | ❌ | ✔️ | ✔️ |
| China North 3 | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| East Asia | ✔️ (v3/v4/v5 only) | ✔️ ** | ✔️ | ✔️ |
| East US | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| East US 2 | ✔️ (v3/v4 only) | ✔️ | ✔️ | ✔️ |
| France Central | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| France South | ✔️ (v3/v4 only) | ❌ | ✔️ | ✔️ |
| Germany West Central | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| Germany North* | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| Israel Central | ✔️ (v3/v4 only) | ✔️ | ✔️ | ❌ |
| Italy North | ✔️ (v3/v4 only) | ✔️ | ✔️ | ❌ |
| Japan East | ✔️ (v3/v4 only) | ✔️ | ✔️ | ✔️ |
| Japan West | ✔️ (v3/v4 only) | ❌ | ✔️ | ✔️ |
| Jio India West | ✔️ (v3 only) | ❌ | ✔️ | ❌ |
| Korea Central | ✔️ (v3/v4/v5 only) | ✔️ ** | ✔️ | ✔️ |
| Korea South | ✔️ (v3/v4/v5 only) | ❌ | ✔️ | ✔️ |
| Poland Central | ✔️ (v3/v4 only) | ✔️ | ✔️ | ❌ |
| North Central US | ✔️ | ❌ | ✔️ | ✔️ |
| North Europe | ✔️ (v3/v4 only) | ✔️ | ✔️ | ✔️ |
| Norway East | ✔️ | ✔️ | ✔️ | ✔️ |
| Norway West * | ✔️ (v3/v4 only) | ❌ | ✔️ | ✔️ |
| Qatar Central | ✔️ (v3/v4 only) | ✔️ | ✔️ | ❌ |
| South Africa North | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| South Africa West* | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| South Central US | ✔️ (v3/v4 only) | ❌ $ | ✔️ | ✔️ |
| South India | ✔️ (v3/v4/v5 only) | ❌ | ✔️ | ✔️ |
| Southeast Asia | ✔️ | ✔️ | ✔️ | ✔️ |
| Sweden Central | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| Sweden South* | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| Switzerland North | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| Switzerland West* | ✔️ (v3/v4/v5 only) | ❌ | ✔️ | ✔️ |
| UAE Central* | ✔️ (v3/v4 only) | ❌ | ✔️ | ✔️ |
| UAE North | ✔️ (v3/v4/v5 only) | ✔️ | ✔️ | ✔️ |
| US Gov Arizona | ✔️ (v3/v4 only) | ❌ | ✔️ | ❌ |
| US Gov Texas | ✔️ (v3/v4 only) | ❌ | ✔️ | ❌ |
| US Gov Virginia | ✔️ (v3/v4 only) | ✔️ | ✔️ | ✔️ |
| UK South | ✔️ | ✔️ | ✔️ | ✔️ |
| UK West | ✔️ | ❌ | ✔️ | ✔️ |
| West Central US | ✔️ | ❌ | ✔️ | ✔️ |
| West Europe | ✔️ | ❌ $ | ✔️ | ✔️ |
| West US | ✔️ | ❌ | ✔️ | ✔️ |
| West US 2 | ✔️ (v3/v4 only) | ❌ $ | :heavy_check_mark | ✔️ |
| West US 3 | ✔️ | ✔️ ** | ✔️ | ❌ |
$ New Zone-redundant high availability deployments are temporarily blocked in these regions. Already provisioned HA servers are fully supported.
$$ New server deployments are temporarily blocked in these regions. Already provisioned servers are fully supported.
** 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.
(*) Certain regions are access-restricted to support specific customer scenarios, such as in-country/region disaster recovery. These regions are available only upon request by creating a new support request.
Note
If your application requires Zone redundant HA and is unavailable in your preferred Azure region, consider using other regions within the same geography where Zone redundant HA is available, such as US East for US East 2, Central US for North Central US, etc.
Migration
Azure Database for PostgreSQL flexible server runs the community version of PostgreSQL. This allows full application compatibility and requires a minimal refactoring cost to migrate an existing application developed on the PostgreSQL engine to Azure Database for PostgreSQL flexible server.
- Azure Database for PostgreSQL single server to Azure Database for PostgreSQL flexible server Migration tool (Preview) - This tool provides an easier migration capability from Azure Database for PostgreSQL single server to Azure Database for PostgreSQL flexible server.
- Dump and Restore – For offline migrations, where users can afford some downtime, dump and restore using community tools like pg_dump and pg_restore can provide the fastest way to migrate. See Migrate using dump and restore for details.
- Azure Database Migration Service – For seamless and simplified migrations to Azure Database for PostgreSQL flexible server with minimal downtime, Azure Database Migration Service can be used. See DMS via portal and DMS via CLI. You can migrate from your Azure Database for PostgreSQL single server instance to Azure Database for PostgreSQL flexible server. See this DMS article for details.
Frequently asked questions
Will Azure Database for PostgreSQL flexible server replace Azure Database for PostgreSQL single server?
We continue to support Azure Database for PostgreSQL single server and encourage you to adopt Azure Database for PostgreSQL flexible server with richer capabilities such as zone resilient HA, predictable performance, maximum control, custom maintenance window, cost optimization controls, and simplified developer experience suitable for your enterprise workloads. If we decide to retire any service, feature, API or SKU, you receive advance notice, including a migration or transition path. Learn more about Microsoft Lifecycle policies here.
What is Microsoft's policy to address PostgreSQL engine defects?
Refer to Microsoft's current policy here.
Contacts
For any questions or suggestions you might have on Azure Database for PostgreSQL flexible server, send an email to the Azure Database for PostgreSQL flexible server team (@Ask Azure DB for PostgreSQL).
Note
This email address isn't a technical support alias.
In addition, consider the following points of contact as appropriate:
- To contact Azure Support, file a ticket from the Azure portal.
- To fix an issue with your account, file a support request in the Azure portal.
- To provide feedback or to request new features, create an entry via UserVoice.
Next steps
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.
Feedback
Kommer snart: I hele 2024 udfaser vi GitHub-problemer som feedbackmekanisme for indhold og erstatter det med et nyt feedbacksystem. Du kan få flere oplysninger under: https://aka.ms/ContentUserFeedback.
Indsend og få vist feedback om