[In preview] Public Preview: In-place major version upgrade to PostgreSQL 17 on Azure Database for PostgreSQL flexible server

-


PostgreSQL 17 In-Place Upgrade on Azure Database for PostgreSQL Flexible Server

Overview

Azure Database for PostgreSQL flexible server now supports an in-place major version upgrade to PostgreSQL 17, currently available in public preview. This upgrade allows users to move from PostgreSQL versions 14, 15, or 16 to PostgreSQL 17 without data migration or changes to connection strings, simplifying the process for users and applications[1][3].

Key Features of the Upgrade

  • No Data Migration Required: The upgrade process does not require moving data, which reduces complexity and downtime[4].
  • No Changes to Connection Strings: Applications can continue to use existing connection strings, ensuring minimal disruption[3].
  • In-Place Upgrade Capability: This feature is designed to minimize user and application disruption by retaining server settings and name post-upgrade[4].

How to Upgrade

Users can upgrade their PostgreSQL versions using either the Azure Portal or the Azure CLI:

Azure Portal:

  1. Navigate to the Azure Portal and select your Azure Database for PostgreSQL flexible server.
  2. Choose the Upgrade option in the left navigation pane.
  3. Select PostgreSQL 17 as the target version.
  4. Review and confirm the upgrade, then initiate it[1].

Azure CLI:

Use the following command to trigger the upgrade:

az postgres flexible-server upgrade \
--resource-group <your-resource-group> \
--name <your-server-name> \
--version 17

This command initiates the in-place upgrade process[1].

Availability and Future Plans

The PostgreSQL 17 in-place upgrade is currently available in select Azure regions, including East US, East US 2, Central US, and West US 3. Broader regional availability is expected as the feature moves towards general availability[1][3].

Latest Updates

The public preview of the PostgreSQL 17 in-place upgrade was announced on May 19, 2025, aligning with ongoing efforts to enhance Azure Database services[3]. This follows the initial preview release of PostgreSQL 17 on Azure Database for PostgreSQL Flexible Server, which was made available for early testing and feedback[5].

อ้างอิงค์ : https://azure.microsoft.com/updates?id=495135

ความคิดเห็น

แสดงความคิดเห็น

โพสต์ยอดนิยมจากบล็อกนี้

Retirement: MICROSOFT AZURE OPERATED BY 21VIANET - Action required to migrate to Azure China North 3 region by July 1, 2026 due to China North 1 and China East 1 region retirement

-
รูปภาพ
Retirement of Azure Regions in China Microsoft Azure operated by 21Vianet is planning significant changes to its regional infrastructure in China. Specifically, the China North 1 and China East 1 regions are scheduled for retirement. Key Points About the Retirement Retirement Date : Both China North 1 and China East 1 regions will be retired on July 1, 2026 [1]. Impact : Customers with services in these regions will experience disruptions if they do not migrate their services to other regions by the retirement date[1]. Recommended Action : Microsoft advises customers to migrate their services to alternative regions, such as China North 3 , to avoid service disruptions. Additional Service Updates Beyond the region retirement, there are other service updates relevant to Azure in China: Azure Batch Service Retirement : The Azure Batch service will also be retired on March 31, 2026 , in regions like India West , China North 1 , and China East 1 , due to regional constraints...
อ่านเพิ่มเติม

[Launched] Generally Available: Private subnet

-
รูปภาพ
Here is a structured summary of the Generally Available: Private Subnet launch announcement and key information from the official Azure Updates page referenced (https://azure.microsoft.com/updates?id=492953): General Availability of Azure Private Subnet Announcement Date: May 2025[1] Feature Status: Launched (now generally available for all Azure customers) Description: The "private subnet" feature for Azure Virtual Network is now production-ready, enabling customers to create subnets with enhanced network isolation and security. Key Benefits: Enhanced Security: Private subnets help restrict outbound internet access, reducing the risk of unauthorized data exfiltration. Explicit Internet Access: VMs in a private subnet do not have default outbound internet access, requiring explicit configuration of NAT gateways or other routes for connectivity[5]. Greater Control: Organizations gain more granular management over their Azure VM network traffic, allowing them t...
อ่านเพิ่มเติม

[In preview] Public Preview: Perth - Azure Extended Zones

-
รูปภาพ
Azure Extended Zones in Perth: Public Preview and Updates Overview of Azure Extended Zones Azure Extended Zones are designed to support latency-sensitive and throughput-intensive applications by positioning them closer to end-users, thereby reducing latency and improving overall service delivery[3]. This technology is particularly beneficial for applications requiring quick data processing and fast response times. Public Preview: Perth - Azure Extended Zones The Azure Extended Zone in Perth is currently in public preview, with a planned full deployment by mid-2025[1][4]. This initiative is part of Microsoft's broader strategy to expand its global data center footprint and enhance cloud services in Western Australia[1][5]. Key Features and Benefits Reduced Latency : By hosting applications closer to users, Azure Extended Zones reduce latency, improving the efficiency and reliability of essential services[1][5]. Localized Services : This technology allows data to be processe...
อ่านเพิ่มเติม