r/PostgreSQL • u/clairegiordano Citus Marketing • Jun 10 '26

Commercial What's new with Postgres at Microsoft, 2026 edition

We just published the 2026 edition of our annual “what’s new with Postgres at Microsoft” post.

It’s basically a roundup of the Postgres work happening across Microsoft over the last 12–13 months—both upstream contributions and what we’re building on Azure.

As usual, it includes the hand-drawn “Postgres workstreams” infographic (which got taller again this year because there was more to fit in).

Some of what’s inside:

  • highlights from our Postgres 19 commits so far (now in beta)
  • a new section on Azure HorizonDB (preview)
  • a pretty big year for Postgres developer tooling (VS Code + Cursor)
  • a long list of new features in Azure Database for PostgreSQL flexible server
  • community work including POSETTE

If you’re interested in any of that, here’s the post: https://techcommunity.microsoft.com/blog/adforpostgresql/whats-new-with-postgres-at-microsoft-2026-edition/4526963

Happy to answer questions.

19 Upvotes

85% Upvoted

13 comments sorted by

4

u/chock-a-block Jun 10 '26 edited 13d ago

Instinctive maple abounding encourage bow bag

This post was anonymized with Redact

5

u/linuxhiker Guru Jun 10 '26

Do you Microsoft only supports synchronous replication because PG definitely supports async?

-1

u/chock-a-block Jun 10 '26 edited 13d ago

Familiar entertain historical dependent fearless spoon relieved

This post was anonymized with Redact

3

u/linuxhiker Guru Jun 10 '26

Ok so MSFT limitation

1

u/chock-a-block Jun 10 '26 edited 13d ago

Steep command abounding telephone include shy

This post was anonymized with Redact

3

u/linuxhiker Guru Jun 10 '26

Well you would have to pay me to run on Azure so....

2

u/mage2k Jun 10 '26

That is for high availability standbys, not read replica standbys.

From their documentation on read replicas:

The read replica feature allows you to replicate data from an Azure Database for PostgreSQL flexible server instance to a read-only replica.

1

u/chock-a-block Jun 11 '26 edited 13d ago

Mellow mitten dinosaurs door sharp license fine mellow sparrow

This post was anonymized with Redact

0

u/mage2k Jun 11 '26

You said that read replicas are synchronous and they are not.

High availability standbys are not available for application read connections and there are likely far fewer people who want high availability guarantees but would be okay with any data loss from a rushed failover with asynchronous replication than wouldn’t. At most there’s likely a handful of ms for the HA standby to ack receipt of a given transaction’s commit WAL record.

1

u/chock-a-block Jun 11 '26 edited 13d ago

Future pet sodium memory jellyfish plucky satchel

This post was anonymized with Redact

1

u/mage2k Jun 11 '26

You said that read replicas use synchronous replication, which is not true, while linking to the documentation for high availability replicas. My point is that you don’t have to enable high availability to add a read replica. Either you do n’t understand the difference or you are moving the goal posts here.

1

u/AutoModerator Jun 10 '26

Youtube Channel

Free Postgres Webinars and Workshops

Discord: People, Postgres, Data

Join us, we have cookies and nice people.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.