{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Talking Postgres with Claire Giordano","title":"What went wrong (& what went right) with AIO with Andres Freund","html":"","width":"100%","height":180,"duration":4366,"description":"Six years, a prototype, and a brief multi-layered descent into “wronger and wronger” design—what does it take to land a major architectural change in Postgres? In Episode 31 of Talking Postgres, Andres Freund—major contributor, Postgres committer, and lead of the Asynchronous I/O project—shares the wins, the missteps, and why he thinks AIO definitely took too long. We dig into io_uring in Linux, direct I/O, streaming reads, technical leadership, and exactly when is the right time to stop working on a prototype. If you’ve ever wondered how big architectural changes happen, or why they sometimes take years, this episode is for you.\n \nLinks mentioned in this episode:\nTalking Postgres podcast: How I got started as a developer (& in Postgres) with Andres Freund & Heikki Linnakangas\nRelease Notes: PostgreSQL 18 release notes \nNews: PostgreSQL RC 1 Released on Sep 04 2025\nWikipedia page: io_uring\nPostgreSQL: Join the PostgreSQL Hacking Discord\nVideo of talk: What went wrong with AIO by Andres Freund at PGConfdev 2025\nCommit: Add core asynchronous I/O infrastructure to PostgreSQL\nWiki page: AIO project in PostgreSQL with state, sub-projects, and work still to be done\nUpcoming Talk: AIO in PG 18 and Beyond at PGConf NYC on 30 Sep 2025\nUpcoming Talk: AIO in PG 18 and Beyond at PGConf EU on 23 Oct 2025\nWikipedia page: XZ Utils backdoor discovery by Andres Freund\nCal invite: LIVE recording of Ep32 of Talking Postgres to happen on Wed Oct 8, 2025","thumbnail_url":"https://img.transistorcdn.com/96oK6oMtH0qfumCURmVA4Hg7enGdZ1swehO6BOYsd8w/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS84OWEw/YmE3ZDQ5MDI3NzA5/MTljZThlODg3N2Qy/M2M1YS5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}