What went wrong (& what went right) with AIO with Andres Freund (E30) #TalkingPostgres talkingpostgres.com/episodes/wha...

🎙️ New @talkingpostgres.com podcast Ep31 just published! Andres Freund @anarazel.de explored what went wrong (& what went right) with AIO in Postgres 18. Featuring io_uring, prototypes, streaming reads, CI, & why it took too long 🎧 talkingpostgres.com/episodes/wha... 📺 youtu.be/bVei7-AyMJ8?...

"I've got several hundred open source projects that I'm maintaining right now. And the reason I'm doing that is purely to make sure I never have to solve the same problem twice." -Simon Willison #TalkingPostgres E30

- October 8, 2025 @ 10:00am PT: Talking Postgres: The Fundamental Interconnectedness of All Things with Boriss Mejías (E32) - November 5, 2025 @ 10:00am PT: Talking Postgres: Building a dev experience for Postgres in VS Code with Rob Emanuele (E33) 2/2

Microsoft Open Source Discord - Upcoming Events (github.com/microsoft/op... ): - September 17, 2025 @ 10:00am PT: Talking Postgres: What went wrong (and what went right) with AIO with Andres Freund (E31) 1/N

AI for data engineers with Simon Willison (E30) #TalkingPostgres talkingpostgres.com/episodes/ai-...

Hello! For those just discovering the @talkingpostgres.com podcast—and those already on this 30-episodes & counting #TalkingPostgres journey with me—we just dropped a new 3-minute trailer (02:52 to be precise) & it is FUN 🔥 🎧 talkingpostgres.com/episodes/tal... 📺 youtu.be/ZWMb9qmTpSY?...

🎙️ New @talkingpostgres.com #podcast Ep30 just published! Guest @simonwillison.net talked about AI for data engineers. We skipped hype & boosterism to chat about Postgres permissions, alt text, 150-line SQL queries, & pelicans on 🚲 🎧 talkingpostgres.com/episodes/ai-... 📺 youtu.be/8SAqeJHsmRM?...

I'm so looking forward to having the amazing @simonwillison.net on the @talkingpostgres.com #podcast again, to discuss AI for data engineers (& #PostgreSQL people) When? The LIVE recording is on Wed Aug 6th at 10am PDT Join us on Discord to be part of parallel live text chat aka.ms/TalkingPostg...

"...even at Microsoft in my first year I worked as a data scientist and in my second year, I made the switch to pure software engineering, to Postgres actually." -Arda Aytekin #TalkingPostgres E13

"I think these are my best days. [...] That's what I prefer to do. Spend a lot of time on tough problems and then find beautiful solutions." -Derk van Veen #TalkingPostgres E12

How I got started leading database teams with Shireesh Thota (E29) #TalkingPostgres talkingpostgres.com/episodes/how...

New blog post 📒 Bits of engineering wisdom from a year of the #TalkingPostgres #podcast 🎙️ ft. highlights from the past year, from past 13 episodes with #PostgreSQL guests like Tom Lane, Melanie Plageman, Bruce Momjian, Dawn Wages, Affan Dar, & more! techcommunity.microsoft.com/blog/adforpo...

🎙️ New #TalkingPostgres #podcast Ep29 just published! Shireesh Thota once dreamed of driving a bus. Instead, he fell for math, BASIC, & engineering—& now leads all database work at Microsoft. 🎧 talkingpostgres.com/episodes/how... 📺 youtu.be/jP8a_S2MjtY?... #PostgreSQL #Azure #VSCode #opensource

Full disclosure: I'm a bit biased. But if you’re into #PostgreSQL (or open source more generally), @talkingpostgres.com might become your next favorite podcast 🎙️ Ep20 with Tom Lane—core team member, major contributor, Postgres committer—is a good place to start 🎧 talkingpostgres.com/episodes/how...

12 years of Postgres Weekly with Peter Cooper (E28) #TalkingPostgres talkingpostgres.com/episodes/12-...

🎙️ New #TalkingPostgres #podcast episode! Peter Cooper joined to talk about 12 years of Postgres Weekly—with QBASIC Usenet fanzines, the BBC big tent, lots of #PostgreSQL, weekly newsletters for 460K devs, & 1 very cheesy story 🧀 🎧 talkingpostgres.com/episodes/12-... 📺 youtu.be/F1eWSAVKxdY?...

Happening Wed 18 Jun at 12noon PDT (new time this time) is a LIVE recording of Ep28 of the #TalkingPostgres #podcast with guest Peter Cooper to talk about "12 years of Postgres Weekly" Join us on Discord for the parallel live text chat aka.ms/TalkingPostg... #PostgreSQL #PostgresWeekly

"I don't like benchmarking, but it's also often one of the highest impact things you can do ... I want to say if you managed to answer the question that you're trying to answer, though, very often the question only starts appearing once you run a bunch of benchmarks" -Marco Slot #TalkingPostgres E11

"Almost everyone that's run benchmarks for a significant amount of time, they built their own sort of automation to run the specific benchmarks they needed to run, & then probably they shared it with people & then no one used it or like a few people used it." -Jelte Fennema-Nio #TalkingPostgres E11

"So one of the problems that we had doing that work was for really high scale sites. Either they had a monitoring system that really didn't cover the things that we needed in Postgres or they had a system like it just couldn't scale high enough." -Rob Treat #TalkingPostgres E10

"...pganalyze when it started out was too small to sustain itself as a company. And so I was essentially running it as a side project. For example, when I was at Citus Data luckily the founders of Citus Data were, very generous in allowing that." -Lukas Fittl #TalkingPostgres E10

"...back in 2006, we started a company. We were using Postgres as our main kind of data store. And we got into challenges into scaling the Postgres database back then. That's many Postgres releases ago. And so of course, replication was, still in its infancy..." -Lukas Fittl #TalkingPostgres E10

"...having spent a lot of time in support for databases was really valuable because that's the organization which talks to users, which talks to customers. So you kind of get the other side of the story as well." -Peter Farkas #TalkingPostgres E27

How I got started with FerretDB (& why we chose Postgres) with Peter Farkas (E27) #TalkingPostgres talkingpostgres.com/episodes/how...

Often my @talkingpostgres.com #podcast guests are from the #PostgreSQL contributor community—but this month it was different! Peter Farkas & team chose Postgres as the engine for FerretDB. Listen to hear Peter's surprising founder story & why they chose Postgres Also: tell your friends! 👀

New episode of @talkingpostgres.com #podcast 🎙️ In Ep27, Peter Farkas of FerretDB shares how a Himalayan trek led to an open source MongoDB alternative on Postgres (& DocumentDB) Plus: FerretDB's original name, and Trappist cheese 🧀 🎧 talkingpostgres.com/episodes/how... 📺 youtu.be/dQfD00bDMqo?...

"So the thing for me is that the work that I do, I never want to have to solve the same problem twice, ever. That's the most frustrating thing is when you sit down to solve the problem. You're like, "wow, I solved this before" and I'm gonna have to do it again." -Simon Willison #TalkingPostgres E01

"I've always been a little fascinated by, making complex things easy to use and simple to understand. And so for me, SQL was that it was filling a gap where some of the things are very complex." -Dimitri Fontaine #TalkingPostgres E09

"One of the reasons is that the committee thinks that users are ill served by claims that the word "structured" accurately describes the language, which it does not. S-Q-L is not very structured, but it is a query language." -Vik Fearing #TalkingPostgres E09

"I think by the time I was around 10, I got my own first computer, which was an Amiga, and I started to learn BASIC on that. And then I started, moved on to C programming. [...] I also wrote a game when I was around 15 with a friend who did the graphics." - Heikki Linnakangas #TalkingPostgres E08

"I think I'd had at least three, four attempts at becoming a developer, as probably many guys in that time, I was impressed by games at first and then tried to write a game and then discovered that I actually don't enjoy that at all." -Andres Freund #TalkingPostgres E08

"PostGIS provided that sweet spot of being affordable and approachable to both the GIS people and also the relational people. So I was from the relational world. Not from GIS. GIS meant nothing to me when I first got introduced to PostGIS." -Regina Obe #TalkingPostgres E07

"No one would say that "I'm a 'jis' professional." They would say I'm a "G-I-S" professional. And GIS is an industry term of art which not everybody knows the meaning of. It stands for "Geographic Information Systems". It's been around as a term since...the mid 80s" -Paul Ramsey #TalkingPostgres E07

Loved having Peter Farkas of FerretDB on @talkingpostgres.com today & can't wait to publish the podcast episode on Fri 🎙️ We covered lots of ground, incl. the value of open source. Even @sogrady.org's recent RedMonk post about the Redis licensing change got a shout-out redmonk.com/sogrady/2025...

"I was an early user of Unix back in the early 90s. I actually had a home Unix server, which was at that time very rare. And of course, at that time, there was very little software available for it. So most everything you ran was open source, compiled it yourself" -Bruce Momjian #TalkingPostgres E26

"I actually studied economics and political science in college, and I got into coding through research. I was on this path to want to be a journalist because I always loved writing analytically, which I also use in my work today." -Chelsea Dole #TalkingPostgres E06

"And I showed up day one and they gave me a connection string and it wasn't to a SQL Server, it was to Postgres... my reaction was, because I was so used to reaching out to the community to find help and to see where I could solve my problems, how I could learn more." -Ryan Booz #TalkingPostgres E05

"You didn't think about Postgres ever, or MySQL or SQLite, which were also commonly used with Rails apps then, and so you would take for granted that it would do data management for you. And I used it for transactions and other things at companies that I worked at." -Floor Drees #TalkingPostgres E06

Why Python developers just use Postgres with Dawn Wages (E25) #TalkingPostgres talkingpostgres.com/episodes/why...

Why mentor Postgres developers with Robert Haas (E24) #TalkingPostgres talkingpostgres.com/episodes/why...

How I got started as a developer & in Postgres with Daniel Gustafsson (E23) #TalkingPostgres talkingpostgres.com/episodes/how...

Leading engineering for Postgres on Azure with Affan Dar (E22) #TalkingPostgres talkingpostgres.com/episodes/lea...

"For anyone who just goes to a conference & only attends...and doesn't network, you're doing it wrong. You need to network. I've actually been going to these conferences and attending the sessions because it's a great way to pick up a bunch of skills quickly..." -Grant Fritchey #TalkingPostgres E05

"I thought I wanted to be a linguist at some point. But I did a fair amount of tinkering & programming, & I kind of wanted to use computers in linguistics. But, at some point a job came up ... they were desperate for a C programmer to finish this computer program." -Thomas Munro #TalkingPostgres E04

Helping Rails developers learn Postgres with Andrew Atkinson (E21) #TalkingPostgres talkingpostgres.com/episodes/hel...

How I got started as a developer (& in Postgres) with Tom Lane (E20) #TalkingPostgres talkingpostgres.com/episodes/how...

Becoming a Postgres committer with Melanie Plageman (E19) #TalkingPostgres talkingpostgres.com/episodes/bec...

How I got started as a developer (& in Postgres) with David Rowley (E18) #TalkingPostgres talkingpostgres.com/episodes/how...

Podcasting about Postgres with Pino de Candia (E17) #TalkingPostgres talkingpostgres.com/episodes/pod...