Flavors of PostgreSQL® and you: how to choose a Postgres
summary
Compares concrete systems: Google AlloyDB Omni claims 100% Postgres SQL compatibility but adds a proprietary vector engine and a columnar store plus an AI/ML worker while documenting internals poorly; AWS Aurora guarantees only end‑result compatibility with a distributed commit log and S3‑backed storage, not Postgres storage layout; Neon is serverless, implements the Aurora whitepaper under the hood and pins compatibility to specific Postgres versions (last five majors); community forms a testable compatibility registry for voluntary publication of results.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker background
- 6:27Talk overview and version history
- 9:39PostgreSQL core architecture
- 10:01AlloyDB Omni deep dive
- 16:21AWS Aurora and Neon explained
- 22:18Separation of storage and compute
- 23:23Corporate influence on PostgreSQL
- 26:32Community compatibility initiatives
- 29:20Q&A session begins
- 30:02Brand dilution and trademark concerns
- 33:57Threats from big cloud providers
- 36:08Advice for non-OSPO companies
- 39:06Compatibility checklist discussion
- 40:32Open source business models
- 42:38Q&A wrap-up and conclusion
related talks
37mFlavors of PostgreSQL® and you: how to choose a Postgres
24mWhy Google Cloud is the Best Place for Your PostgreSQL Workload
01h 02mDiamond Sponsor Hall
51mHow Postgres is Different (read BETTER than) your database
29mPostgres Demystified
30mPostgreSQL—more relevant than ever
14mBuilding a better PostgreSQL together
39mAWS Aurora