Flavors of PostgreSQL® and you: how to choose a Postgres
summary
Compares concrete systems: Google AlloyDB Omni (forked Postgres with a columnar engine and extended vector indexes, Docker image that’s a black box and thin docs), AWS Aurora and Neon (serverless, storage/compute decoupling, “end‑result compatibility” rather than binary compatibility), and upstream Postgres 17 (incremental backups and JSON tables) plus extensions like PostGIS, TimescaleDB and CloudNativePG. Recommends AlloyDB for GCP shops needing lightweight columnar or remote Vertex model queries; Aurora/Neon for global low‑latency availability with vendor lock‑in; vanilla Postgres for portability and full extension access.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:49What makes Postgres Postgres
- 6:02Understanding Postgres flavors
- 8:53AlloyDB Omni overview
- 17:23AWS Aurora and Neon
- 25:46Postgres 17 new features
- 27:31Extensions ecosystem
- 31:02Why vanilla Postgres now
- 32:47Forking and Postgres community
- 34:10Q&A
related talks
43mFlavors of PostgreSQL® and you: how to choose a Postgres
24mWhy Google Cloud is the Best Place for Your PostgreSQL Workload
01h 02mDiamond Sponsor Hall
49mCan PostgreSQL Compete with Analytics Specialists?
47mPostgres & Beyond
29mPostgres Demystified
51mHow Postgres is Different (read BETTER than) your database
56mBreakout Session