Player FM 앱으로 오프라인으로 전환하세요!
What went wrong (& what went right) with AIO with Andres Freund
Fetch error
Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on November 07, 2025 20:05 ()
What now? This series will be checked again in the next day. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.
Manage episode 507360378 series 3488768
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.
Links mentioned in this episode:
- Talking Postgres podcast: How I got started as a developer (& in Postgres) with Andres Freund & Heikki Linnakangas
- Release Notes: PostgreSQL 18 release notes
- News: PostgreSQL RC 1 Released on Sep 04 2025
- Wikipedia page: io_uring
- PostgreSQL: Join the PostgreSQL Hacking Discord
- Video of talk: What went wrong with AIO by Andres Freund at PGConfdev 2025
- Commit: Add core asynchronous I/O infrastructure to PostgreSQL
- Wiki page: AIO project in PostgreSQL with state, sub-projects, and work still to be done
- Upcoming Talk: AIO in PG 18 and Beyond at PGConf NYC on 30 Sep 2025
- Upcoming Talk: AIO in PG 18 and Beyond at PGConf EU on 23 Oct 2025
- Wikipedia page: XZ Utils backdoor discovery by Andres Freund
- Cal invite: LIVE recording of Ep32 of Talking Postgres to happen on Wed Oct 8, 2025
34 에피소드
Fetch error
Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on November 07, 2025 20:05 ()
What now? This series will be checked again in the next day. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.
Manage episode 507360378 series 3488768
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.
Links mentioned in this episode:
- Talking Postgres podcast: How I got started as a developer (& in Postgres) with Andres Freund & Heikki Linnakangas
- Release Notes: PostgreSQL 18 release notes
- News: PostgreSQL RC 1 Released on Sep 04 2025
- Wikipedia page: io_uring
- PostgreSQL: Join the PostgreSQL Hacking Discord
- Video of talk: What went wrong with AIO by Andres Freund at PGConfdev 2025
- Commit: Add core asynchronous I/O infrastructure to PostgreSQL
- Wiki page: AIO project in PostgreSQL with state, sub-projects, and work still to be done
- Upcoming Talk: AIO in PG 18 and Beyond at PGConf NYC on 30 Sep 2025
- Upcoming Talk: AIO in PG 18 and Beyond at PGConf EU on 23 Oct 2025
- Wikipedia page: XZ Utils backdoor discovery by Andres Freund
- Cal invite: LIVE recording of Ep32 of Talking Postgres to happen on Wed Oct 8, 2025
34 에피소드
모든 에피소드
×플레이어 FM에 오신것을 환영합니다!
플레이어 FM은 웹에서 고품질 팟캐스트를 검색하여 지금 바로 즐길 수 있도록 합니다. 최고의 팟캐스트 앱이며 Android, iPhone 및 웹에서도 작동합니다. 장치 간 구독 동기화를 위해 가입하세요.