Azure infographic showing PostgreSQL Flexible Server with Intel v6 and AMD v6 compute options, plus temporary and persistent storage.
Azure Database for PostgreSQL Flexible Server has a new generally available option. Intel and AMD v6 compute tiers with a local temporary disk are now listed as "Launched" in Azure Updates. The feed item is dated November 17, 2026. This is a compute-portfolio change, so it affects sizing and cost choices more than it affects how PostgreSQL itself behaves.

Azure infographic showing PostgreSQL Flexible Server with Intel v6 and AMD v6 compute options, plus temporary and persistent storage. What Microsoft announced​

The Azure Updates wording says the v6 generation expands the Flexible Server compute portfolio. Microsoft's Ignite-week database post says v5 and v6 deliver more transactions than v4 SKUs and use less CPU to do it. The listing says customers can pick Intel or AMD v6 options to suit their workload. They keep the same Flexible Server management experience.

The "temp disk" in the title is the key detail. Microsoft's Ignite-week blog says traditional compute SKUs include a local temp disk, used for temporary files when sorts, joins and index builds outgrow available memory. The new GA item keeps that disk. It sits alongside the new diskless tiers, which are a different product.

Temp disk versus diskless​

Two v5/v6 variants now exist, and the same Microsoft post sets out the trade-off between them:

  • Diskless SKUs: These are provided without a temporary disk at a lower price point.
  • Temp-disk SKUs: Microsoft still recommends these for larger analytical workloads that generate temporary files. For OLTP workloads, or analytical workloads that fit in memory, Microsoft says the diskless SKUs perform as well at lower cost.

The Azure Updates listing for the diskless v5 tier (not v6) also carries a November 18, 2026 date in a third-party roadmap tracker. The two announcements are clearly meant to be read together.

Practical reading:

  • If your queries regularly spill sorts, hash joins or index builds to disk, the temp-disk v6 tiers are the ones Microsoft points you toward.
  • If your workload is a typical transactional application that stays in memory, the cheaper diskless option may be worth testing.
  • These are Microsoft's own positioning claims. Test them against your own workload before moving production.

Hardware background​

Earlier Microsoft material describes the v6 General Purpose and Memory Optimized SKUs. It says they run on 5th Gen Intel Xeon and AMD fourth-generation EPYC 9004 processors, scaling up to 192 vCores and 1.8 TiB of memory. That comes from Microsoft's "What's new with Postgres" 2026 post. It was published before this GA entry, so treat it as background. It doesn't confirm the exact SKU list for this launch.

What the announcement doesn't say​

The Azure Updates entry gives no benchmarks, SKU names, region list or pricing. I couldn't confirm any of these:

  • Which regions offer the temp-disk v6 tiers. Microsoft's Ignite post gives a regional rollout for the separate Confidential Compute v6 SKU. Intel-based SKUs started in 5 regions and AMD-based SKUs in 23. That figure doesn't apply to this GA item.
  • Whether any earlier preview limits still apply. Microsoft's service overview has described V6 preview limitations, such as no scaling between V6 and Burstable. I couldn't verify whether those carry over to the GA tiers.
  • The capacity or performance of the local temporary disk.

Check the Azure portal in your target region before planning around any of these.

How to move an existing server​

Microsoft's general scaling procedure for Flexible Server applies, though I couldn't confirm it covers every transition to the new v6 temp-disk options. In the portal:

  1. Select your Flexible Server.
  2. Open Compute + storage in the resource menu.
  3. Choose a compute tier.
  4. If your region supports both Intel and AMD, use the Compute processor option to filter the Compute size list by manufacturer. (Microsoft's scaling page describes this filter.)
  5. Pick a size and select Save.
  6. Confirm the restart prompt if one appears.

Microsoft's scaling documentation warns that a scaling request restarts the server and makes it unavailable for some time. Schedule the change for a maintenance window and rehearse it on a non-production clone first.

With the Azure CLI, the documented command is az postgres flexible-server update. It takes the --tier and --sku-name parameters. Allowed SKU names depend on the tier and region. An invalid value returns an error listing the supported names. That error is a quick way to see which v6 SKUs your region offers.

Storage is separate​

This change doesn't alter how data is stored. Microsoft's storage documentation says provisioned storage holds database files, temporary files, transaction logs and server logs. The local temp disk is a separate compute-side feature. Don't assume it is persistent, because Microsoft's limits page says the service can't guarantee that custom temporary tablespaces survive restarts and HA failovers.

Bottom line​

For administrators, the news is that production-ready v6 Intel and AMD options with a local temp disk now exist. Their price and performance claims come from Microsoft and are unquantified in the listing. Before resizing, compare the SKUs and prices available in your region and check for temp-file spills in your workload. Also benchmark the diskless alternative, and plan for the restart.

 

References

  1. (Launched) Generally Available: Intel and AMD v6 with temp disk for Azure Database for PostgreSQL Azure Updates 2026-11-17T23:52:49Z
  2. Release Notes for Azure Database for PostgreSQL flexible server - Azure Database for PostgreSQL docs.azure.cn
  3. Scale Compute in Azure Database for PostgreSQL Flexible Server - Azure Database for PostgreSQL | Microsoft Learn learn.microsoft.com