Pushing Postgres Forward: From Open Source Contributions to Intelligent T
summary
Microsoft reports 540 commit attributions in PG18 out of 3,320 total, reviews by Microsoft account for 18% (~1,000 of 5,000) of reviews, and PG18 async IO cuts system calls by batching 8KB reads so sequential scans run noticeably faster than PG17. Partition planner changes make planning ~3× faster at ~56 partitions and far better at thousands. Tooling includes a VS Code extension with ~200,000 installs, autonomous index tuning on Azure that requires ≥20% win for one query and ≤10% regressions, and DiskANN + PQ vector search outperforming HNSW.
AI-written summary · about
chapters (20)
- 0:00Introduction and survey
- 0:22Microsoft’s Postgres contributions
- 1:04Postgres community events
- 3:12Possest conference details
- 4:17Talking Possest podcast
- 5:02Annual Microsoft Postgres blog
- 6:05Core Postgres contributions
- 8:49Asynchronous IO subsystem
- 12:22Other PG18 improvements
- 13:29OAuth and partitioning
- 15:14Early multi-threading work
- 16:59VS Code extension features
- 22:00Azure Postgres services
- 22:43Citus and elastic clusters
- 25:51Vector indexing on Azure
- 27:37Semantic operators
- 29:24AI examples and repositories
- 31:32Autonomous index tuning
- 34:25Commitment to Postgres
- 35:08Q&A session
related talks
24mAll The Postgres Things at Microsoft, POSETTE edition
16mAll the Postgres Things
22mKEYNOTE: Driving Postgres forward at Microsoft
21mWhat Microsoft is Building for Postgres in 2025
26mPostgreSQL 17 vs 18: Side‑by‑Side Performance Wins in Real‑World Queries
30mOvercoming Performance Hurdles in Postgres Partitioned Tables
34mPostgres 10, Performance, and You
07mKeynote: Contributing to Critical Open Source Projects: Lessons from PostgreSQL