Azure Database for PostgreSQL now supports asynchronous replication of data from one Azure Database for PostgreSQL server (the ‘master’) to up to five Azure Database for PostgreSQL servers (the ‘replicas’) in the same region. This allows read-heavy workloads to scale out and be balanced across replica servers according to your preferences. Replica servers are read-only; any writes are those replicated from data changes on the master. Stopping replication to a replica server causes it to become a standalone server that accepts reads and writes.
Access generally available functionality in the Azure Database Migration Service to migrate Amazon RDS for PostgreSQL to Azure Database for PostgreSQL while the source database remains online during migration.
You can now replicate data from a single Azure Database for PostgreSQL server (master) to up to five read-only servers (read replicas) within the same Azure region. This feature uses PostgreSQL's native asynchronous replication.
Use Azure Database Migration Service to migrate PostgreSQL databases hosted on-premises, on a virtual machine, or on AWS RDS PostgreSQL, to Azure Database for PostgreSQL while the source database remains online during migration.
Today, we are excited to announce the general availability (GA) of Azure Database for MySQL and Azure Database for PostgreSQL for Azure Government customers. With this GA milestone, government agencies and their partners have even more options as they work to advance their missions. These fully managed, government-ready database as a service offerings bring the community versions of MySQL and PostgreSQL to mission-critical government workloads with built-in high availability, a 99.99% availability SLA, elastic scaling for performance, and industry leading security and compliance. Building on the community edition of MySQL and PostgreSQL, lifting and shifting to the cloud is easier than ever, while maintaining full compatibility with your languages and frameworks of your choice.
With the general availability of the Azure Database for PostgreSQL service earlier this year, a new stable API version was released to allow customers to manage all aspects of the new vCore and storage model.
The preview APIs do not support all aspects of the updated pricing model and will be retired by December 1, 2018. All customers who use the preview APIs must switch to the new API version by December 1, 2018. Any operations executed with the preview APIs will fail.
If you are using an Azure Resource Manager template or a REST API, ensure that the API version is not marked with the suffix "-preview."
Customers can now move existing Azure Database for PostgreSQL servers to either a new subscription or a new resource group in the same subscription. This functionality provides customers with the flexibility to manage their PostgreSQL resources by using different resource groups and subscriptions. Learn more about how to move servers by using the Azure portal, Azure CLI, and REST API.