


28 Oct 2026 · 1h 46m · 35 chapters

Craig Kerstiens (Snowflake) argues “the future is Postgres” by combining Postgres core stability with powerful extensions and highlighting why Postgres 19 is a standout release. He focuses on PG Lake (an open source extension) that brings Iceberg catalogs plus embedded DuckDB into Postgres to query Parquet/Geo Parquet in S3, reducing ETL glue and operational overhead. He also covers Postgres 19 features: Repack concurrently, query plan pinning, and “group by all,” plus broader SQL/standard additions like graph properties.
Craig Kerstiens leads Postgres efforts at Snowflake. Previously helped build data platforms at Heroku, Citrus Data, Microsoft, and Crunchy Data. He has long bet on Postgres, including early support at Heroku when others weren’t.
Postgres stays “boring” and predictable in core while extensions enable specialized capabilities (text search, PostGIS, and PG Lake). PG Lake blurs OLTP/OLAP boundaries by letting transactional Postgres read analytics formats directly. Postgres 19’s operational improvements (reclaiming bloat without locks, controlling plan changes) make it especially compelling for production. AI-generated PRs are overwhelming the small Postgres committer set (~50).
PG Lake’s “turtles all the way down” stack (Iceberg catalog + DuckDB + SQL/function conversion + Geo Parquet conversion + extension version cascade). Postgres 19’s Repack replacing PG Repack/Squeeze extensions; plan pinning to avoid planner surprises.
Written by AI. May contain mistakes.
Discussion on the significance of Postgres and its evolving popularity.
“And we also talk about the small group of roughly 50 committers who keep it all running and how a ton of agent-generated PRs are landing on their doorstep.”
Exploring how Postgres has become an attractive choice for developers.
“Well, friends, we are back with an old friend and a good friend.”
Discussion on the narratives around Postgres and its competitors like MySQL.
“And I think Postgres itself deserves, in a way, even more credit.”
Insights on the operational aspects and community behind Postgres.
“Like Oracle, MySQL, Oracle Database, MariaDB, the whole division there to sort of like, I guess, set the ground at unease back in the day?”
The importance of extensions in Postgres and new developments like PG Lake.
“To keep the language simple and let things happen in user land that need to happen in user land and let core be core and boring in a way.”
Learn how Postgres extensions simplify data management complexities.
“How do we convert from Geo Parquet to like Geo data types in Postgres?”
Explore the fundamental differences between OLTP and OLAP systems.
“And that's like database academic stuff, like online transactional processing, online analytical processing.”
Discuss the challenges and costs associated with moving data between systems.
“It's a source of, so when you go and scan all the data from a row based store, right?”
Learn about DuckDB and Parquet, their roles in analytics, and their benefits.
“You got hundreds of your web servers connecting to a high concurrency, massive scale, right?”
Understand Iceberg's functionality and its impact on data management.
“out, you know, a million records of purchases from my database to a flat file.”
Discover how Postgres integrates with Iceberg and DuckDB for enhanced analytics.
“And now it's automatically going to store the data in these Parquet files in S3.”
Explore the capabilities of Postgres as a comprehensive data platform.
“I don't even have that particular knife.”
Discover how PG Lake simplifies data management for developers.
“I kind of want all my data mostly in one place.”
Learn about the allure of Postgres extensions and its thriving ecosystem.
“They didn't care at all that they spent three months that they're just going to throw this out.”
Gain insights into the new features and improvements in Postgres 19.
“I'm like, guys, this is like a, this is a small research paper right here.”
Understand the importance of Repack for managing database bloat.
“And so Postgres under the covers is a giant, like a pen-only log, right?”
Explore how customer feedback influences database product management.
“we're not into, you know, cattle, we're back to pets, right?”
Discover the new graph capabilities in Postgres 19 and their implications.
“One person on my team, Tom Lane, I mean, I love Tom.”
Learn about the latest enhancements in Postgres, including graph properties and upsert functionalities.
“time, I think it's actually we're getting cool stuff too.”
Discuss the growing preference for Postgres over traditional databases like Oracle in enterprises.
“I'm not thinking about geeking out on my database.”
Explore the implications of AI on the development and maintenance of Postgres and databases in general.
“Do you know how much the court, like, what do you know behind the scenes at all?”
Discuss the evolving role of DBAs in a landscape dominated by open source and AI-driven development.
“And people learned to develop and could, you know, code an app and literally go get a job, right?”
Discussing the increasing demand for database expertise amidst rapid advancements in applications.
“If it was 10 to one before, now it's 100 to one.”
Exploring how AI and intelligence can influence the future of database management, particularly with Postgres.
“I mean, just yesterday, thank you very much.”
Examining the dual nature of open source in relation to visibility and security challenges.
“Like, it's a fascinating time that I really feel for the, you know, I'm close to it, obviously, but like that Postgres ecosystem, you know, continuing to thrive.”
Debating the pros and cons of using C versus newer languages like Rust in the Postgres ecosystem.
“and a bad thing when it comes to the visibility of these things and cybersecurity.”
Understanding the importance of community contributions in identifying long-standing bugs within Postgres.
“And so I trust it's out of a solid spot, right?”
Insights into the testing processes and contribution opportunities within the Postgres community.
“If it was a ground zero kind of a brand new project, Greenfield, you wouldn't write it in Go.”
Learn about the challenges and responsibilities of disclosing vulnerabilities in open source projects.
“We don't want to advertise it before we've got their point released.”
Explore the future of Postgres, including predictions and new features.
“It's like, well, it's the database that everyone's going to use under the covers, right?”
Discover how to get involved with the Postgres community and contribute.
“you know, I know we mentioned PG Lake, how to get there, et cetera.”
Learn how to get involved with the Postgres community and contribute.
“what JavaScript framework has lasted more than two, right?”
Discuss the impact of Postgres on new developer tools and frameworks.
“The, you know, remind me how to get involved on mailing lists.”
Understand the importance of company contributions to the Postgres ecosystem.
“Yeah, no, I think it's interesting to me because I see so many folks that are doing, like, you know, I love the Supabase folks.”
Hear about the host's preferences for database choices in production.

Get the gist, explore an idea or ask about something said.
On The Changelog: Software Development, Open Source, what are the key points of this episode?
Automatic transcript. May contain errors.
0:00What's up, friends? Welcome back this week on The Change. I'm talking to my good friend Craig Kerstiens. Craig leads the Postgres efforts at Snowflake, and he previously helped build data platforms at Heroku, Citrus Data, Microsoft, and Crunchy Data. Of course, we're back for the year of Postgres and why it might finally be true. Craig bet on Postgres back at Heroku when nobody else would, and he's been geeking out at it ever since. We discuss PG Lake, the open source extension that puts an iceberg catalog and embedded DuckDB inside Postgres so you can create parquet files in S3. So cool. We get into why Postgres 19 might be the coolest release in a decade with repack concurrently, query plan pinning, and group by all.
0:48And we also talk about the small group of roughly 50 committers who keep it all running and how a ton of agent-generated PRs are landing on their doorstep. A massive thank you to my friends and partners at Fly.io. Computers for agents. Sandboxes, y 'all, are not enough. Give your agent a real computer and get back to building. Learn more at Fly.io. Okay, let's do this.
1:31This episode is brought to you by our friends at Coder.com. You know what? Your developers, they have guardrails. The humans, guardrails, right? That makes sense. But your AI does not. How often are you running your AI dash dash dangerously? I think that most people are living a little dangerous. Some are sandboxed, some are not, most are not. And I'm here with Nicky Pike, Field CTO for Coder. So Nicky, what is the focus right now for Coder?
2:01Craig Kerstiens: I mean, really our focus and what we're doing at Coder is on the governance around AI. So, you know, everyone right now, they're talking about, you know, AI agents like they're magic, but nobody's really asking where they run and what they have access to or what happens when one gets compromised. I mean, kind of give an analogy, you're not going to invite a contractor into your home and then leave and have them have full access to your safe and everything else on day one. You know, this is what people are doing with agents. We are wanting to, we are the infrastructure that helps you put guardrails and restrictions and governance around agents and what they're doing to you today.
2:35Craig Kerstiens: That's where Coder succeeds because, you know, we started out as a CDE company. There's no secret. We were a CDE company. We created remote dev environments, standardized workspaces. But what we realized is that we accidentally built the exact foundation for the AI age before the AI age even really arrived. So isolated, governed, audible compute environments, that's what we build. And that's exactly what enterprises need when their workforce starts, including agents alongside their humans. So, you know, for us, this wasn't a pivot. This was really, we finally found the problem that perfectly fit with what we'd already built.
3:10So if you're living dangerously, dash, dash, dangerously, non-sandboxed, you name it, Coder has AI governance for you, a centralized gateway to observe and to control LLM tool usage across your environments, authenticate model requests, audit every prompt, and contain agents behind a default deny allow list. The smart way. Learn more at Coder.com. Request a demo. oncemorecoder.com.
3:58Well, friends, we are back with an old friend and a good friend. And I've missed you, Craig. So it's just been way too long. i think postgres is more is it always just a little more at the epicenter of what we're all thinking about i feel like it's always the the uh the boring but provocative topic for us what do you think yeah yeah no i think that's like spot on it's uh there's one uh reporter i talk to that every year comes back to me he's like craig i'm sorry i'm doing it again and he writes this article that it's like, this is the year of Postgres. And it's been like the year of Postgres for like five years in a row.
4:42Right? It's like, all right. The same for Linux though, right? And I feel like it's finally, they're sort of both incrementally becoming the year of. But it's funny for me, having like been here for so long of like, you know, we picked Postgres back at Heroku long before it was cool. In fact, like no one else wanted to bet on Postgres. And everyone was like, why on earth are you doing this? Right? and it wasn't cool then. And it's like, you know, I have no misconceptions of what I do for work. I'm a nerd, right? Like I run databases for a living. And so like, you know, when my kids take me to school, I'm not going to win the like coolest, like, you know, hey, let's talk about your parents' jobs.
5:21Like I'm not. You know, I don't know about that these days though. You know, I think now the nerd dads are the cool dads. Maybe when we get to high school, I mean, for elementary school, I don't know that you're winning, you're beating out the, But it's like Postgres became sexy. Can I say a database is sexy? I mean, you can if you want. It is America. But it's like right here now, I mean, it's been fun to see this because investing in it 15 years ago, who else was then, right? And actually to have a small hand in it getting to where it is is exciting and fulfilling in that journey. And I think Postgres itself deserves, in a way, even more credit.
6:05I think now that it's gotten so popular, so many people are latching onto it. And I want some of that Postgres coolness. And yet, Postgres itself is just so freaking solid and good. And to be fair, though, as devs, I was at a conference a few years ago. And we were at the speaker dinner. And as engineers, we try to pretend we're so principled. And they were like, you know, as a Python developer, like, obviously I'm going to pick Python. I would never use Ruby. Who on earth would use Ruby? And yet they're basically the same language. Like, I know I'm going to have pitchforks coming for me. Basically.
6:51Yes, there are differences. I'm with you on that because I'm just immediately that person. So don't feel bad. I'm sure there's going to be some pitchforks. I'm like, I am stopping this episode right now. He said Python and Ruby were the same. This guy knows nothing about technology. Matt's listening, just yelling in Japanese right now. And yet, like, you know, and it was funny because they went on and were like, for example, Postgres for MySQL. And this is 10 years ago. They're like, because I'm a good Django developer, of course I pick Postgres. Well, I mean, I'm a real engineer. I make good decisions.
7:25Why would I ever pick MySQL? What taste, man? And yet, they're like. I care about my future. In reality, they were like, you know what? I actually don't know why I'd pick one versus the other. And it was really funny because the table got quiet because half the table knew me. And like, oh, because of, you know, concurrent index creation, transactional, GDL, listen, notify, you know, JSONB. Like, they're like, oh, that's really cool. I should go learn about some of this stuff. And I think like, you know, it's awesome to see that now the world is kind of embracing everything that is in there and we're learning.
7:59But also I think there's still a little bit of sometimes that, you know, again, I'm probably going to get pitchforks of like, you know, we're bandwagon fans. We pick Postgres because it's the age of Postgres and we don't always peel back the onion of what's so great about it. Well, sometimes story plays a role in that. Is that critical to you at all? Like Oracle, MySQL, Oracle Database, MariaDB, the whole division there to sort of like, I guess, set the ground at unease back in the day? I mean, you've been in the game for a while. So was that a role for you? I'm sure. I mean, there's no way it didn't help, right?
8:40I think part of it was like, it kind of became the default for Ruby developers on Heroku, right? Like that was a time. Yeah, very influential. Like rest in peace. Distribution of ideas, man. Yeah, definitely rest in peace, Heroku. And like, cool, great. And then it started to become cool with those features, right? And back at Heroku, we invested and wrote some checks for core development features, right? And hired those folks way, way back. And I continued to do it at Citus and Microsoft and as part of Crunchy Data and now Snowflag that it's like, cool. Like want to contribute and make the core better.
9:18But definitely, you know, Oracle with MySQL and MariaDB definitely helped. But I'm often asked, like, okay, well, if I wanted to create a company and recreate what Postgres is, like how do I do that? like how does how is postgres what it is i'm like i wish i knew right like they you don't right there's not a issue tracker for it like there's no like things don't get pushed up to github with prs they mail patches to a mailing list like do you know how to generate a patch to send to a mailing list i'm not sure i do right like i don't think i do know how to do that honestly get it just continues on like eventually they like they mirrored the repo to github so people could see it right so they didn't have to go like pull it up but it just works and it's the test of time i wish i could say how you could repeat this because by all accounts this should not work and yet it really just keeps getting better and there's huge kudos to like you know all of the core developers that believe in they believe in postgres more than they believe in most things right and want to see kind of the see Postgres continue to live on and it's over 30 years old what's 30 years old besides Linux that we're talking about well I think uh even when when I've read your stuff over the years the one thing that I keep hearing you say is extensions keeping the core boring keeping it predictable keeping a core contract in place secure fast things like that things that really make it like you said sexy the unsexy side of which i think is actually sexy to me those are features right those are curves and so i think about software like that so you have this core and then they call that user land it's extensions and then anyone can kind of make postgres their own version of postgres maybe even postgres compatible okay but whatever right so like what do you do you not believe or maybe you do believe since you said it a few times, that extensions is really where it is allowed to thrive because it doesn't force the core function, similar to the Go language, to keep it simple, right?
11:32To keep the language simple and let things happen in user land that need to happen in user land and let core be core and boring in a way. Yeah, I mean, yeah, I love extensions. I think they're the next, I mean, what we should come back to in a few minutes probably is Postgres 19 itself. because I don't want to diminish the core. And like, man, if there was ever a release that is just like, wow to me, it is, Postgres 19, I think, is the coolest release that we've had in maybe 10 years. But to your point, yeah, extensions are absolutely amazing. And I think you look at people that, you know, there's now multiple different text search extensions, right?
12:14So that, you know, BM25 kind of text search can be in Postgres, right? This is kind of the core of what Elasticsearch does and makes it so great. You know, ParadeDB was the first one there. There's PG Tech Search, which is, you know, fully open source from Timescale, which adds that capability, right? There is, you know, PostGIS, which now... There's a stream match on Accent. I mean, the list goes on, right? Yeah, I mean, PostGIS is massive. It turns it into this whole other... PostGIS is a fascinating one because everyone's like, oh, that core team has to talk to the other core team. And it's like, they do, but they're also running on this parallel path because what you do for geospatial is so different than the rest of core Postgres, and it's this massive extension.
13:02I mean, we open-sourced PG Lake back in November, which, oh man, to me, it's like a work of art. It's actually like 12 extensions in one. So pgLake is like the overarching extension. But like we started with putting an iceberg catalog inside Postgres. And they're like, hang on. That's like an open file format parquet files. Like that's column base. And that's talking to S3. What's that got to do with Postgres? And it's like, well, it's just a catalog. But once we have the catalog there, okay, great. Well, we need something to query this. So we embedded DuckDB inside Postgres. Get out of here. Yeah, it's turtles all the way down, right?
13:47And so, but hang on, DuckDB has a different SQL syntax. So we have an extension that converts from Postgres SQL syntax to DuckDB. But hang on, DuckDB has different functions. So we have an extension that does that. Well, what about the Geo Parquet files, right? How do we convert from Geo Parquet to like Geo data types in Postgres? So we have an extension for that. And so - You're getting all hot and bothered over here. Now we've got 10 extensions that run with different versions. And what happens when you bump one version that doesn't work with another? So we have an extension. A cascade of change.
14:20We have an extension that manages the versions of extensions. Right? Now, you're like, oh, great. I'm glad you love to create all this complexity. But the result is like, I can literally now just go and query a parquet file and load it from like S3 into Postgres. So I don't need the traditional like, great. I don't have this Python script running on a box below. it's literally just running with pgcron inside my database and for data engineering they've had these tools for a while but inside your transactional Postgres database no, it's always this duct tape and glue and I don't even have to load it I can actually just there's elegant pipelines that people are setting up now that great, just drop off this stuff in my data lake in this S3 bucket and I just want to query the new files as they are there just shows up which is like like huh i never thought about doing this before and it's like what happens when you bring like duck db and parquet into the world of postgres like what what changes there and can you maybe just for the uninitiated kind of give a a version of what duck db and parquet do like why those are querible fast yeah yeah let me let me back up right so like Like we've lived in this world, like this 30-year-old divide of like OLTP versus OLAP, right?
15:42And that's like database academic stuff, like online transactional processing, online analytical processing. The reality is like, you know, OLTP, operational databases are row-based stores, right? They store a whole row together, whereas analytical systems are typically column-based. And so what you do is you store a whole column so that you can summarize that column as the entire – You're not getting the whole row most of the time. It's like, how many, you know, how many sales did I have in this book from Amazon yesterday, right? Well, I don't need to know across all books. I just need to know, you know, some, all of this book, right?
16:19That's very different than I need all the order details for all the books, right? So, you know, OLTP, row base, often single row inserts and updates and lookups, right? Like I log into Amazon and place my order. that's the order going into Amazon, right? And, you know, really fast kind of inserts, heavy indexing on them, right? Like good old B-tree indexes in there or GIM indexes, like advanced indexing. But you want the query plan to be incredibly fast and like leverage indexes and then get your data back in, you know, single millisecond, right? Like this is just what Postgres does. Yeah. completely different from the OLAP world, right?
17:04Which is, I don't mean anything in one millisecond. I want to know this report from Amazon.com, how many orders were placed yesterday, right? Like, I'm okay with taking that a few minutes. It's a lot of, you know, how you organize the data. Data gets batch ingested. It gets split into partitions. Like, this is the world that Snowflake lives in and all these data warehouses, right? And they've lived in this world for a long time. These worlds are like Mars and Venus. I've seen these teams, I've almost never seen these two different teams in the same meeting. I think they hate each other, right?
17:42Because one's running the production operational system. Now the other one's just trying to do their job and give the analytics insights and drive the business and make decisions. But man, they're kind of at, one of my colleagues joked that he's pretty sure the E in ETL stands for evil. Oh gosh. Which I, I loved it because it's a necessary evil. We haven't gotten away from that. Help me unpack that one. Why evil? Give me more details on that. It's a source of, so when you go and scan all the data from a row based store, right? You're exacting load on it. And like, you're doing this batch pool, which is not ideal for.
18:17And so you're often like creating unnecessary load and oftentimes outages, right? So while you're doing that, your walls backing up on Postgres, you've got latency in getting the data into your analytics system, it's costly. Moving data from one system to the other is a huge source of pain. I usually start talking to people about this and they almost start crying. Yeah, I've been dealing with this for so long. But you can't be like, nope, I'm not going to move my data between these two systems because it's painful. You can't just be like, I protest. Can you just throw more machines at it or more of more?
18:55to it and sort of crush some of that or more compute i guess it's more cost right more costs especially you know what's lazy computer so expensive these days man it's and so not so much but discs and ram ram's climbing it's i mean all of it's climbing so ram is three times the price uh that it was a year ago i mean that's just consumer level that i've got i'm not purchase powering you know a data center so i'm purchase powering a dev lab so my even in my mileage the the costs have risen three times i mean if you want to buy four terabytes of mvme storage this moment one single one you're gonna bust out a thousand dollars at least maybe more uh for a decent mvme drive that's worth the iops and worth the speed and yeah you can throw more at it you keep throwing more at it and keep throwing more but it's like you know this is this is a pain we've lived with for a while and so kind of getting back to the like okay hang on what's duck db right um yeah the most simple parallel i can give right is duck db is like sqlite but for analytics right so you've got sqlite as your lightweight embedded transactional database right it's great for local stuff right i want to ship a small database around um i i want to embed something but sqlite most people aren't saying like that's my production Postgres replacement, right?
20:20Postgres is a server process. You got hundreds of your web servers connecting to a high concurrency, massive scale, right? And so you've got DuckDB, which is closer to SQLite, which is great for my desktop analytics. Like, I'm just me. I want to do some stuff, right? More powerful than Excel. I like SQL. It's really good as an embedded analytical database. So that's what it's good at. So it knows how to speak all of these columnar formats, right? And so Parquet is an open standard just, you know, Parquet file. Iceberg is metadata on like, you know, think of if I copied out, you know, a million records of purchases from my database to a flat file.
21:04Right? Like think of Parquet as a CSV file, but it's designed for columnar analytics. Great. But what happens when I've canceled my Amazon order? Well, uh-oh, I've got to go write a new file now, right? And so where Iceberg comes in, which is kind of the new cool hot thing in the data analytics space, open file format, right? So it says, oh, well, here's this parquet file, but here's this update set, and here's this deletion set, right? So you can stack these together. So now I've got like, if this were the Postgres analogy, it's like, and this is a poor analogy, but it's like, oh, well, if I've got like CSV and then change sets of CSVs and change sets of CSVs, well, sort of now I've got a database that's live, right?
21:50Yeah, you got like some version of history, right? It's a version of change, as you just said there. But yeah, that's interesting. Okay, so I hadn't heard of Iceberg yet. Oh, man, so I got someone you should talk to next, right after me, for like a deep dive on Iceberg and what it means for this whole world, right? And they're just flat files then? These Iceberg, they're just essentially change files into a barcade file? So Iceberg is a catalog with metadata about the Iceberg, about the Powerclay files, right? That basically turns it into like, great, now someone can just go and connect to a Iceberg catalog and know how to query it.
22:25All these data warehouse engines. Interesting. So open source file format that in the data warehousing world and data analytics world, you can go and query. So, okay, what's Postgres got to do with this? Why do we have DuckDB? Well, now Postgres can go and create these Iceberg files. So now I can go inside Postgres and go create table, orders, and all I have to say is using Iceberg. And now it's automatically going to store the data in these Parquet files in S3. I can insert into it like normal. I can query it like normal. When I query it like normal, for PG Lake, it's going to use DuckDB to query it, which is going to be fast analytics, right?
23:07Now I can also go and connect this to things like, you know, Spark and query it directly from there, from Snowflake, from whatever things that can speak Iceberg, which most analytics products can. So now I just like blurred this line to wait. HostGress understands analytics, can write out analytics. And I had this gap, right? This like bridge now over this gap of like, well, these are disconnected systems. well now they can be shared right and now i have this for me pg lake is this like you know the next question is like okay that's really cool engineering but when do i use this right and just like scratching my head like i've never thought about this stuff before what are my options now um and this is just like one extension but like for me pg lake is this like swiss army knife i'm like like yeah i've used the pocket knife in my swiss army knife i'm kind of use the screwdriver like i'm curious have you ever used the corkscrew to open like when you're out camping I think are you just packing like two bottles of wine and like now I need my Swiss army knife to open.
24:10Almost never. The corkscrew and the toothpick are the two things in the Swiss army knife that I'm like, who's reusing that toothpick. I would be reusing that toothpick. It's metal. It's fine. Yeah, it's metal. I thought it was plastic. It's a plastic. I would assume it's metal. The little tweezers there are metal. Okay. I don't even have that particular knife. I was just following you assuming it was metal. because most knives or most Swiss Army knives are made of metal. Well, I mean, everyone I've ever had. I mean, all the other parts are, yeah. Right. So, I mean, there's a lot in there. So you can see there's disparate weird parts that you're just not sure of and how you'd ever use them, but then you kind of find a useful way.
24:48But then there's also the obvious ones, right? Right, like the knife. You never know when you're out camping and there is someone with a bottle of wine and if you have the Swiss Army. Like, you're not carrying a corkscrew, right? But I've got it in there. Pause one second. I have got a Swiss Army knife. You've got wine. We prepare ourselves. This is a camping trip success right here. Man, I'm looking forward to our camp out this holiday weekend. Right. So that's just one extension, right? Which to me is awesome. And you're like, hang on. What is Postgres? Postgres has no business doing this. That's a whole ecosystem world on a database is what you're saying.
25:26You can explore PGLake for a while. You can specialize for the next year. maybe even the next several parts of your years as part of your career, especially as data becomes more and more centerpiece for everyone, really. And you didn't have to really go learn a new database or system. It's still just Postgres. It's actually a Postgres extension post-GIS, like geospatial or time series or text search. Like, what about vector storage? right like man that world of extensions and i think for me it's also interesting because it is open source you're not locked in right when someone's like oh i'm postgres and like prove it to me right like show me that you're an extension or you're actually contributing to postgres versus like i'd you know i speak the wire protocol okay that's great until i need logical replication well well but do you really like yeah i do right like this is postgres and i think it's for me from a philosophy perspective like one it's an exciting frontier but I think it's also from a philosophy perspective it's making the community better like it's giving back it's better together how we win It's almost like with extensions Postgres is its own version of an OS like a runtime not quite an OS and not quite not a runtime either you can almost do if you can build an extension for it You can do it on Postgres and because it's open source and because of the way it's ran, that is a very interesting superpower because you can sort of like center your entire fleet, your entire team on one database versus many databases and bring those databases like Parquet files or DuckDB or these unique formats that have very specialized places, but not necessarily you wouldn't think of them as a Postgres.
27:26straight, so to speak. But now you can because you have extensions and you can do those things. It's a really interesting power that it has. I've never quite often said it's like a data platform. Postgres is not just a boring relational database. It's a platform. I think thinking about it as almost like an OS, like you're saying, like a runtime. I think it's actually a beautiful way of articulating it. Just in that case there alone with PGLake, you can expose yourself to something that you'd have to build a sidecar to, not an extension or something that was like a siloed database, which is the worst scenario to be in in any scenario where you're a developer.
28:07You're like, no, no, no. I kind of want all my data mostly in one place. Obviously, I want backups and different stuff like that. But operationally, I don't want to have to think about seven APIs or seven credentials that get rolled or who has that blessing or that grant and you just get to you know you get all sorts of issues in that scenario where if you can roll in through pg lake having duck db and parquet is is that and then s3 i mean if you can that's just amazing like that um i'm gonna have to play with yeah like like if you can do like 80 or 90 as good as a this a separate special purpose thing but you don't have to operate it and run it and maintain it like it's reduction of costs but i think more importantly it's a reduction of pain, right?
28:55Like monitoring, you know, one system, one backup, you know, one run book, one fail time. I mean, one of a lot, but I'm sure you have an N plus in there somewhere, but not having to learn five things or three things or two things to get a job done. You're just doing one. Yeah. I mean, I've seen some, it was funny. I was talking with one person when I showed them PG Lake when we announced it. And they're like, we were about to go live on this whole kind of pipeline using, I think it was Athena and some other things. They'd been working on it for three months. They tested it. It was working well enough.
29:33They were planning to go to production in the next few weeks. They're like, man, I'm going to throw all of that out and use PG Lake. This is so much simpler. This is great. I just felt so bad because they've been this massive project of three months of engineering. I'm like, I'm sorry we didn't talk to you. sooner, that we could have planned for this. And they're like, don't feel bad at all. I was so worried about that thing going to production and how I would operate it that I'm happy to delete code. They didn't care at all that they spent three months that they're just going to throw this out.
30:04I think there's a beauty in the simplicity of it. There's a lot of advanced engineering on it that's really, really cool. But how you work with it, it's just standard old SQL. It's pretty straightforward. it's pretty like my favorite type of engineering is when you take all that advanced stuff you do the hard stuff but the end user experience I mean this was back to the Heroku days right? Get Push Heroku Master was beautiful and I still haven't I don't think people have recreated that sense that simplicity right? Not yet! When you take that advanced stuff and make it so simple right? Which is my entire goal of what we're doing with Postgres Yeah, something magical happened there.
30:47I mean, it was a different world, too. No one could run in the cloud anything. I mean, even to launch a Ruby app, to deploy something was the, well, I can run that here. And that was also in the day when we began to do less of FTPing and copying to actually, you know, true CI, true CD, which is a whole different kind of thing there. um well i know you're on the tip and you mentioned postgres 19 which you recently penned a post on the snowflake blog about um you could probably go there if you want to i'm really interested in this extensions world just because there's so much you can do there but i feel like we've obviously mined that quite a bit uh with pg lake and whatnot but certainly lots of cool stuff happening in the extensions world i think the the point there was really just like this is what makes postgres be so attractive to folks because you can you can build something like pg lake or use something like pg lake on top of postgres and it's a whole entire ecosystem within an ecosystem and then a runtime idea like that to me is what's always been attractive with uh with postgres for me and it seems like uh we haven't destroyed postgres along the way you know it's still thriving yeah it runs well you know there's lots of scenarios where production is challenging and i'm sure you know that quite well with your background you can allude to that but what's a good next space uh pga postgres 19 or something else what are you thinking yeah postgres 19 i mean i we kind of transition easily from from extensions to that like i you know i read this post i'd love for people to check it out but it was funny because i thought it was too long as i was talking about all the features and as soon as i published it there were several folks that were like you've missed my favorite thing in the release.
32:35I'm like, guys, this is like a, this is a small research paper right here. Like this is, you know, this was long and they're like, oh, but you missed this one. Like normally every Postgres release is like, all right, performance got better and we added this little kind of nicety and that sort of thing. And I'd have to go back to
32:58probably Postgres 12 when we added JSON support and we cheated. And everyone's like, oh, like, die no sequel. But, like, Postgres 12, we validated the text on JSON. No, no, sorry, not 12. 9.4. 9.2. No, now I'm going back. Too far almost. 9.4 was JSONB. 9.2 was JSON. Okay. So that was almost 14 years ago. 2010, yeah. 14 years ago, we got JSON and Postgres. I have a secret. We cheated. Finally, it's out. We validated it was valid JSON and threw it into a text field. And every headline that came out that year is like, Postgres is now a document database. And I'm like, well, I like the headline, but it's like, no, this is not like actual JSON compressed.
33:56There's no indexing for it. But man, the headlines were great, right? Like, hey, long-glood Postgres, it's now a document database. Two years later, we got JSON-B. I love my colleague Will describes it as the B stands for better. It's a binary representation of JSON on disk. You can have like gen indexes. So man, this is probably the biggest release in 10 years since JSON-B. And one of the, to me, the flagship things is Repack. And so Postgres under the covers is a giant, like a pen-only log, right? And so you delete a record. It doesn't delete the record and free up the space. It just marks it as dirty.
34:40And it comes back in and, you know, hey, you write a new record, it can overwrite that, right? But that's where you have bloat. Like you delete 100 records and new things are coming in. Well, I've got this 100 records of unused space, which is bloat, that's not going to get reclaimed immediately, right? until you hold a lock and run a vacuum on your database. And so there were a couple of extensions for years, PG Repack and PG Squeeze, that would go in like under the covers, rewrite these tables, free up the vacuum. It's an online operation, but you need extra disk because it's doing all this magic.
35:15They're like somewhat risky to run. Like this is definitely expert mode, right? Of like, all right, I need to run Repack because I have high bloat, but I don't want to take a lock and pause writes and run vacuum. And so like this is hardcore production databases, advanced, you know, management of them. But like repack just is like, all right, we're adding it to core and we're adding repack concurrently. So I can not hold a lock on that and it can run into background. And now this is just like going from advanced power user to, I wouldn't say the like, you know, 101 level stuff, but much more like 201, 301.
35:55now I don't even need this extension that like was out here in the ecosystem. Right. So we've taken that from broader ecosystem to in the core. You don't have to go grab the extension. It's just there, which man, if you've ever used PG repad or PG squeeze or dealt with kind of high bloat and tweaking vacuum, like boom, your life is just bad. And this is one of those things that's like, when you're having a bad day, hey, you're having a really bad, like, this is back to, yeah, I know what's going on with my, we're not into, you know, cattle, we're back to pets, right? Like when we named our servers, like, yeah, I know what's going on with that database.
36:34Like, it's not some random UUID. Like, I know those first few characters with that UUID of that database to say, oh, this is the problem one. This is production. This is what we care about. If you're dealing with that, like, you're in, you're in a good territory because you got some good data and you got a good business going on underneath it, right? But like repack coming into core and repack concurrently, like huge. Like that's like one of five things, right? Like the thing I got called out for so much was like missing hints in Postgres. And so like Oracle is well known for this. Like you can say like, I want you to use this query plan.
37:15Postgres for the longest time has been like, no, the planner is probably better than you. Trust the planner. Trust the planner. It's not dumb. Now, what's fascinating is, like, usually that's correct, except for in this weird case where, like, some new data distribution changed, right? So Postgres undercovers is doing so much magical stuff. Like, it records, like, the number of records in the table, and it has, like, heuristic on the distribution of that. So should it use an index or should it, like, scan the entire table, right? you've got like five types of indexes from like Btree to Gen to Gist to Space Partition Gist to Brin indexes.
37:58And it knows when to use this one, when to use that one, right? And so when you issue a query, it's creating this plan of here's how I go and access all the data. And it's usually really good at that. Now, as your data distribution changes, it may be like, uh-oh, I need to take a new plan now. Well, if you've got a really mature production database, you may say like, you know what i want you to keep using this plan forever don't change don't surprise me right because there was a slight change in the stats or some new like spike of things and you think all the data's changed and it hasn't right so now you can basically not go around the planner and manually say no no i want to tell you what plan to use but like no i want to pan this plan to this query don't change in the future and surprise me and on a large-scale production system like Often when that plan changes out from under you, you're surprised, you're firefighting, you've had a bad day.
38:54One of those things that just keeps getting better. As an operator of databases, it took me a long time to come to terms with running products. Usually if you go ask customers if they have questions or feedback, they're like, I don't like the color blue you used. The roundedness on this button is terrible. Why on earth would you use that font? I was like, hang on, hang on. I just wanted to know, could you click the checkout button and did it work? I wouldn't ask them for it. Usually you ask for product feedback and you're overwhelmed, right? For probably the first 10 to 12 years of my career, which makes me feel old, I'd go ask customers that I was running their database if they had feedback.
39:43And they're like, nope, I'm good. now I'm in my head I'm like okay the only time I've ever done that was like I was so pissed at Hilton for screwing up my reservation that I'm like I'm swapping the Marriott right like the only time I'm like no I don't have feedback is like I'm out the door right I'm I'm like I'm going to sleep at night and like like cold sweat like man I bet they're leaving tomorrow like I can't I like if they deprovision like I knew it I saw it coming but no you don't want to think about your database. Like, it's like my bank. Like, I wanted to just run and work. Like, when's the last time you went into the bank and you're like, tell her, thank you for being in my bank today.
40:26Never. Yeah. The thankless job of being good, I suppose. Being good and being boring. You know, no surprises, no drama, no extras. And so, repack, hence like, the improvements to autovacuum are huge. And logical replication, when you're replicating from Postgres elsewhere, just gets better and better and better. Postgres 19 is pretty magical there. And kudos to all of the Postgres core developers that just kind of keep doing this. They're not the masses of the world that we talk about. They're kind of there hidden. One person on my team, Tom Lane, I mean, I love Tom. He just works on Postgres, and that's just what he wants to do, and just make it better.
41:15And Tom helped work on TIF, the image format, then JPEG and PNG, and when I say worked on, co-authored the spec for lib PNG, for PNG, and then co-wrote lib PNG. He's like, hmm, I'm getting kind of tired of this image thing. Let me take a look at this Postgres thing. I wonder if I can work on that for a little while. and now he's like a significant like percentage of every postgres release and just happy doing it right like the the thankless work of of open source that man postgres is continuing to power the world and that's awesome and it just keeps getting better and better and better at the same time, I think it's actually we're getting cool stuff too.
42:06Now there's graph properties coming to Postgres. You're like, wait, hang on. How does that... It's a SQL database. It's not a graph... Nope. That's gotten approved as part of the SQL standard is graph properties. And now we have SQL graph stuff directly in Postgres as a Postgres 19. Wow. Which is just like, wait, hang on. Now I don't need a graph database and I have text search extensions. Do I need elastic and time series? Do I need a time series database and vector? It's, um, it's, it's really like deep dive on this group by all like, Hey, if you don't want to group by every column, um, one of my personal pet peeves in writing SQL.
42:53So you can do like, you know, select from where and you can go group by and you can number the columns you say group by one two three four and it'll be like the columns from the select terrible never do that it's one of my bad habits because it's like it's easier than retyping the column name um but for like readability for someone else and if they go and move one of those now it's completely changed like the yeah like the result, right? Because you've reordered it. It's such a bad habit. I think I wrote a post on my SQL bad habits. Not my SQL, but my personal SQL bad habits. I had too much fun with that name.
43:34Group I All, now you don't have to even put the columns, right? Like, oh man, that's really nice when writing SQL now. Upsert, right? Insert and on conflict update. Now you can actually get the return. If you want to say insert on conflict, don't do anything. Insert this, but it's already there. Don't do anything. It would just return. But as a developer, I probably wanted that row. Well, insert this or do nothing. But tell me the row that's there so I can do something with it, right? Right. Because it's like create or get. Well, now your ORM doesn't have to then go to two things. It just, like, now that it ties that down to better SQL efficiency.
44:19And it's like, oh, this is actually all making my life better. At the same time, back to that, like, the best database is what I don't think about, right? Like, I want to build apps. Like, I want to build cool features. I'm not thinking about geeking out on my database. But, like, Postgres is that foundation that you can just, like, bet on. What's fascinating for me is also that enterprises are coming along for now. I think in the developer world, we've seen this for a while, right? Like, you ask a developer, like, yeah, of course, Postgres. But now enterprises are like, why would I continue to bet on the high license of Oracle or SQL Server?
44:57Like, Postgres can do all this. Like, we can make this long-term bet, and a fresh out of school, like, grad doesn't want to be working on, like, a DB2 server. But, like, yeah, Postgres seems kind of cool. Yeah.
45:41Everything. They're changing what we ask of Kubernetes. Take identity, for example. When an agent calls an API, they run some code or it touches a database, who's actually authenticated for that action? Well, Abdel S., one of the chairs of the conference, tackles this very question in his keynote, the identity crisis. Who is the AI agent in your cluster? And Jeffrey Sika steps back with Cloud Native, built by humans, engineer to evolve and he's looking at how the open source community adapts to AI and Lynn's son asks cloud native without limits what can AI agents do for us this includes agents that help debug and operate real systems so if you're planning to attend as I mentioned before deep discount generous discount I asked them to give you something special and they agreed so the code to use is changelogpod.
46:41Once again, changelogpod, all lowercase when you register. Head to kubecon.io. That's K-U-B-E-C-O-N.io. Select the North America event, check out the schedule, and register. And use that code. It's a deep discount. I worked so hard to give you that. And they agreed. So use it. Once again, kubecon.io.
47:13This is a new world we're in, too. I mean, I think with a database that can scale like this and be so usable by many and a database you could bet on, as you said, in a world where people are composing more and more components that would not normally be together, together, meaning just maybe in this case here with PGLake, not the perfect example, but somewhat of a good example. good examples like you're willing to bring in a different database and parquet files the same thing with a maybe a go developer it's like no way would i ever be like typescript okay like nah okay but you see more and more teams because of the speed and the ability of of the models letting you play in different lanes you would not normally play in or commingle languages and run times where you would not normally let them run and explore even how, how is this changing maybe the development of Postgres?
48:14Do you know how much the court, like, what do you know behind the scenes at all? If any like is the contribution of the advent of models, you know, making developers 10 Xers, 100 Xers, you know, the super engineers becoming super, super, super engineers kind of thing. Like how much of that is playing into this Postgres world? Yeah, I think it's a really challenging one for something like Postgres, right? I think there's sort of an inflection point right now where I don't know how it's going to pan out. And part of that is like, look, you look at the people contributing kind of AI slop, right? And now for a small team of Postgres of less than 100 kind of people worldwide that are actually committing, contributing to Postgres itself, As committers, closer to actually 50 people of committers that have a commitment to Postgres, now they're overwhelmed with PRs they've got to sort through.
49:12It's easy for, hey, I'm not a great front-end developer, and I don't know TypeScript, but now with a model, I can generate a pretty good UI. I don't think it's the same for C code. right I don't think because the models are trained on so the amount of code out there right that the more code they can learn from the better like there's not a lot of like open source public C code that exists as a great model right like so I think it's actually a challenging inflection point for the Postgres like core team and committers and community itself of like they're sort of overwhelmed with like new people showing up with sometimes slop.
49:54And like, how do we validate correctness, right? How correct are the models? Because, you know, on a UI, on a button misplaced, it's one thing, very different than, uh-oh, I corrupted my data, right? I saw a little bit on Twitter, it'll always be Twitter for me, that like a lot of folks operating like production pipelines haven't hardcore shifted to like, yeah, I'm not going to look at the code and I'm not going to understand the code. and I'm like only AI, like, hey, I'm just going to, you know, orchestrate it and it's going to, I think there was a, you know, a tweet I saw about like, hey, look how much Spotify like deploys.
50:35It's like 7 ,500 times per day. I saw that too. And then I saw the Prima Jimi and it still sucks. Yeah, and I'm like, and it's been broken more. I saw so many folks be like, well, this explains so much. I'm like, the app hasn't really changed. it's often more broken now than it was a year ago oh my gosh yes and yeah the amount of commits and the amount of throughput for a team is not synonymous with the quality of the software now it can be but it's not in that case okay i'm not trying to be negative to spotify engineers by if you're in a spotify engineer i'm not downplaying your hard work what i'm saying is that that doesn't contribute to it being better software.
51:18I think you have different challenges that everyone knows about with Spotify that is probably above your pay grade or above your role that you control. So I'm not saying you in particular, whoever's listening. I'm curious on your take. Think of it like Postgres is your bank, right? Do you want your bank to go AI everything or in reporting your balance and deposits?
51:45What's your take there? Like in the R &D. Yeah, absolutely. Explore in the R &D, you know, like literally in R &D slash wherever that's at for you, like whatever that computes to for your organization, for sure. Innovate, explore, but don't do it in production. Don't do it with my bank data. Don't do it with my, well, do it with my loan because maybe the bounce goes to zero. I mean, go either direction, go up and down, right? Oh, yeah, it could go up. Like, oh, yeah, we accidentally charge you more interest. I think for certain things within the bank, like, hey, show me deals and offers. Like, use AI where you can find savings for me, right?
52:24Like, hey, cancel AT &T and swap to T-Mobile. And it's like, cool, great. There's definitely an area there. But on my core database, I think I'm not there yet, right? And so I think there's, and again, it comes back to like these models are trained on the amount of code that exists. And Postgres is written in C. I haven't written C in a while. I did it back at university, but that's probably the last time. And a lot of people that have written C, like, hate writing C. And I've heard people are like, oh, but I really like Postgres C. Like, the standards for it are so good. It's almost unique that it's like, oh, I can understand this and follow it.
53:04It's managed to maintain that bar that I think, like, you know, but it's going to be an interesting journey, right? because, you know, we weren't talking about AI like this a year ago. Really, we had this inflection point back in November, December timeframe of like, man, these models really have gotten good, and it looks different. And, you know, it's week by week, month by month on how it evolves. I have sympathy for the maintainers, though, of the influx of like new PRs coming in, that they've got to manage and diffuse, and how do you – there's open source that's for sure i mean like the landscape of it i mean it i'm i'm not sure what to think about the next few years of open source like we will still have more open source and will it will still happen it's going to change it's going to keep happening but i think you're going to see more and more overwhelm more and more demand i would say like a pr is a demand for attention right you got a user out there somewhere who's got a problem whether it's slot problem or not it is a problem and because of the groundswell we have more users to have more problems and so you have more prs because you got more people who are motivated to get their problem solved and hey it's open source right so let me share my thing but it's also one of thousands in some cases if not tens of thousands in other cases i think especially on the data side because i think you look like if you we've been on this journey and i had a realization a few years ago that like Like, you know, boot camps were a thing, right?
54:40And people learned to develop and could, you know, code an app and literally go get a job, right? Like, go to a boot camp for three months, come out, you're an engineer, you get a job.
54:51And 15, 20 years ago, you wouldn't make a change to the database without it flowing through a DBA. Like, they controlled the database, how it worked, what queries ran. Like, it flowed through them. They held the keys to the castle to the database. And then we had more developers saying, great, I'm not going to go through the DBA. I'm just going to spin up a database. And then suddenly the DBA is supporting it, right? Because, oh, this is in production. Well, now the DBA is responsible for security, patching, reliability, all that. So they're now running all these databases that developers just spun up.
55:24They didn't get to control, like, was it a good schema design or what the database was. And, okay, that got worse for DBAs. but as we've had this growth of developers, which is awesome, I love it, right? Back to my early Hiroku days, like we had this idea of citizen developers and I think with AI, it's just everyone is one, right? Yeah. That's the point I was trying to make is like you have a groundswell of developers that were problems is where we're at right now. And yet we've never had boot camps for DBAs with like that ratio of like developers but not experts on databases. If it was 10 to one before, now it's 100 to one.
56:04It's about to be a thousand to one of all these apps running that need database expertise on top. Like it's going to be an interesting time of what's this mean for the data ecosystem and how does it adapt? Yeah, I mean, I don't want to throw one more agent into the bucket, but I mean, DBA could be database agent, right? I mean, we are in an era where we could literally put an agent of some version of intelligence. Maybe I'm going to get a pitchfork here at the top of Postgres, you know, like the planner, for example. It doesn't have to be a good algorithm. It could be literally intelligence, like a just-in-time review of the pros and cons of this plan versus B-treat, whatever.
56:46Yeah, yeah. You know? No, I think it's a hard and good question because to your point of like you said, well, do it on R &D, but not on my prod bank account. For sure somebody else should be doing this, R &D this. It is the future. It will happen. Yeah, I think it's when do we get there, right? How fast does the prod get there? How do we adapt to it? How do you adopt this? You know, you can, from an organizational standpoint, you can do it in a lot of different ways. I won't speculate them all, but gosh, there's a lot of ways you can do that. And eventually it will get boring. Like right now, it's so provocative.
57:17Right now, it's so not boring, right? Like every day you look at Twitter slash X and it's something new. I mean, just yesterday, thank you very much. We got Fable 5 back, you know, just so everyone's clear. It's, you know, yesterday was July 1st, July 2nd. And the government shut down Fable 5 access. I don't know if you've played with Fable 5 much, Craig, but I'm curious to hear what you think. But, you know, this model is so different than others and the way it thinks and the way it looks at things. And then, wow, it just drives me crazy when I'm so not a cybersecurity terrorist. And it shuts down on me because it's like, no, no, no.
57:55I just asked you to look at the software, OK? I didn't ask you to do anything bad. I can't help with it. Somewhere in the software, I'm trying to do secure things, which is, you know, crypto or, you know, not like literal crypto, but like cryptography on like a password or something like that or hashing things or moving data. or creating a, you know, content address storage kind of thing, whatever it might be. Like, no, no, no, those are cryptography things and cybersecurity related, but I'm not trying to build a digital bomb here, okay? But anyways, I digress. No, I think it's, you know, all of that has real impact for, like we were saying, to open source, right?
58:30And how is it created? How is it maintained? Like, it's a fascinating time that I really feel for the, you know, I'm close to it, obviously, but like that Postgres ecosystem, you know, continuing to thrive. And how does it maintain that? Cause it's such a small set of folks. Right. And Postgres has such this fast footprint. So, I mean, you know, for me, a big kudos to all the committers on doing that generally thankless work. Right. And, you know, you don't know who they are. Like they're just out there doing the good work cause they love Postgres and it stood the test of time. So it's like, Hey, it just kind of had its 30th birthday.
59:07Jay, here's the next 30 years for Postgres. I mean, if I was a strategic thinker, which I think I might be a little bit, if I wanted to get access to some C code that I've never had access to, or I guess in this case, since it's open source, we do. But I would be curious about how some of the labs like Anthropic or OpenAI are looking at a code base like Postgres and an ecosystem like Postgres to one-handed a model to secure it, because that's the one challenge we're going to have extremely in open source is visibility. And so it's secure by default because it's so visible, but it's also so insecure by default, because you can see with state-of-the-art models now and scan and discern at record spaces we've just never been able to do before.
59:57So I feel like open source is like a good thing and a bad thing when it comes to the visibility of these things and cybersecurity. but I'd be curious to know how many memory leaks or bugs are inside of Postgres because of the choice of C is a great language, but a lot of folks are moving to Rust for safety and things like that. So it's not easy. It would be basically impossible or an undertaking of major magnitude to move Postgres and the world of this from C to Rust, for example. it's a fun discussion that pops up on the mailing list every every couple years like oh i'm just gonna re-platform it in rust like it's like good luck cool yeah have fun with that um i don't know maybe it happens you know never say never i mean the models are getting complicated maybe you know they're getting impressive maybe they can go you give fable five a good plan it'll do some cool stuff for you man if it doesn't get stopped by the security stuff i mean it really it really can and do some amazing things.
1:00:57I don't know that I even want to know the token cost of it, you know, to do a conversion like that. But yeah, no, I think we've definitely seen as a community, like legit bugs come up that have been there for 10 years, 15 years, 20 years. But I think like the broader, because Postgres is so pervasive, so many people have been looking at it, been running their scans. They are contributing back, right? And so I trust it's out of a solid spot, right? And we're continuing to, you know, every new model comes out, focused on scanning, running, where we can contribute. Large enterprises are making big bets, right?
1:01:38So if it's just one of those, there's a lot, you know, Amazon, Microsoft, Google, across the board, folks making big bets on Postgres. And it's not like it's a, oh, this is a 10-person kind of open source project that it's a library that I'm using that there's not... Everyone's using Postgres, right? Like every Fortune 500 has probably a Postgres footprint. Governments are using it. It runs the TLD.org, like the.org TLD domain runs on Postgres. So yeah, it's going to have eyes on it. And I trust that it's like, oh, we're not going to miss some obvious thing. It's battle-tested. It stood the test of time.
1:02:27But yeah, it is fascinating. Paul Ramsey, who's the primary maintainer of PostGIS and author of it, is on my team. And he's like, yeah, I ran against, I think it was Opus 4.6. And he's like, or no, I think it was submitted. He's like, yeah, someone found a bug in some code. It's been there for 15 years. It's like not massive bug, but like small memory leak 15 years there like he's like that's been there since i probably first committed it like way way way back and like man he's just especially with c right like you gotta manage all that memory yourself right you're doing all that whereas rust is doing it for you uh go is obviously garbage collected you know these are things you don't have to think about when you when you write go or rust now you wouldn't write postgres maybe you wouldn't go but he'd probably be better off if you were starting postgres today from zero literal zero So probably Rust, right?
1:03:20If it was a ground zero kind of a brand new project, Greenfield, you wouldn't write it in Go. I mean, you could, but it would be smarter to write it in Rust for the long-term sake of it and the safety of it and just efficiency of it. But yeah, I mean, you've got to manage a lot of that memory, all that memory yourself. And so if you've got many developers, what do you know since you've employed and had as employees or, you know, colleagues in organizations you've run. What do you know about, you said battle testing, and this is stuff I don't have any clue about. And I imagine because the contribution to Postgres is so distributed, meaning it's not one consolidated place where Postgres work happens.
1:04:07It sort of happens everywhere and integrates through the beauty of, or like a beauty of Git. what is it like to battle test postgrass like what is the test suite like where does ci run how do we know like are there certifications for part of it isn't these are things i just never thought about i do think about like hardening particular parts of the code base or maybe even thinking about deterministic simulation testing because maybe you can't do that uh with physical compute. It's just a lot easier to simulate it. Is there anything like that that backs Postgres in ways? Has anyone contributed a large amount of compute to do deterministic simulation testing?
1:04:49A database is a prime place where you control time, network, etc. So I'm just curious about that kind of stuff. What do you know? Yeah, there's several pieces to it, right? And so the Postgres nonprofit Postgres foundation has its own build farm that a commit goes, spins off, it runs, comes back with a bunch. Postgres, you can download the debug stuff and run the build to debug. People run static, it's C, so running static code analysis against it's pretty nice. Back as part of Crunchy Data, before we joined Snowflake, we helped author the stig, which is like, oh, here's how to secure this, right?
1:05:33With like the, um, this like CIS benchmark is another one of like, here's how to securely deploy this and like test for all of these things, right? Which are like all those security check boxes. Like there's a whole process and kind of investment there. Um, the other thing is like when a new release comes out, like if you want to contribute to Postgres and get your hands dirty, the biggest thing you can do is test stuff when it comes out. And so like, there'll be like a beta a tag of like new features and everyone's like we need testers more than anything else everyone's like oh yeah i want to contribute to postgres let me go write some patches i'm gonna write this stuff it's like actually need more people testing and so you can go and like sign up to like test review the code evaluate the feature and so there's basically like phases in a release process for postgres where it's like all right this is the commit fest all this is committed i've reviewed it I've tested it.
1:06:26I've validated it. I've looked at the code. I've tested it. I've run other kind of regressions against it or benchmarks. And I'm thumbs up on it. And so usually at a commit fest, that's where things make it in or don't. I forget the timing. Maybe try to dig it up and put it in show notes. But yeah, if you want to contribute to Postgres in a small way, like, hey, I don't know C, but I think I can read it and test some stuff, jumping into a commit fest is a pretty fun time to learn. But yeah, Postgres community has its own build farm, own CICV that runs, and then a bunch of companies do additional testing, right?
1:07:06Like we do that. I'm sure Amazon does. I'm sure Microsoft does. What does the UOL do? Snowflake is huge. I mean, like what kind of battleground, battle tests, you know, war room. I don't know. How extreme do you get when you name these things? What is that for Snowflake? How do you keep this code? It varies. There's a lot of this for us kind of on the performance side, right? Of like, what's this point release versus that one and major versions? Like, where are regressions? Like, for us, it's a lot of the performance side is a big piece. But then it kind of does vary based on what we're doing as well.
1:07:41Yeah. We've also done plenty of scanning on the, you know, the other sides. I don't know how deep I can go on, like, what scans we're running and where. But, like, we do have a lot of that and take a high pride on, like, that security side of, like, how secure is it? Where are vulnerabilities in it? That sort of thing. Yeah. And I mean, I'm not actually exposing any crown jewels or secrets or anything like that. But is it any that reported back to the Postgres community is like a pulse, so to speak? Because I mean, like the way I think of it is almost like information and universities where they do labs and tests.
1:08:14Like you're kind of like a university with labs and tests. Sure, you're a very fortunate for profit company. I'm not saying you're a university, nonprofit, or not so much profit. Anyways, what I'm trying to say is I feel like Postgres is obviously this open source thing, and then you get the benefit of using it. So how do you give that kind of awareness back to the community about how much you trust Postgres? Yeah, there's a few pieces to it, right? We're going to say we're adding a new extension, right? Right. Well, first, we're going to do our own scan, right, with all of the models and otherwise in our own, you know, security assessment.
1:08:53Before, that used to be manual security assessment, right? Now, it's heavily automated with AI and tools of like, all right, what are the vulnerabilities, right? Are they critical, high, medium, low? And we're going to actually, because usually I'm old, I've known these folks for a long time, right? It's a small community. I'm usually just going to call someone up and say, like, hey, we found these vulnerabilities. How do you want us to report them, right? Because sometimes it's like a well-established project like Postgres and there's a clear process. Sometimes it's an extension that's one person, right?
1:09:21And they don't have a security kind of reporting line. And so it's like, hey, by the way, also we're going to show up with pull requests to fix this, right? It's not just like, hey, I'm going to file the GitHub issue and wish you luck. We believe in being really good stewards of open source, right? That's, to me, pretty important and I think core to us. and we have a team that contributes to Postgres itself. And so we're going to show up with that patch. We're going to ask, how do you want us to disclose this? And sometimes they're like, great, just file the issue, show up with the patch, and we'll, you know, if we need to make a CD out of it, we will.
1:09:57And sometimes it's like, oh, no, this is, you know, this bad. We don't want to advertise it before we've got their point released. That's a big one, right? It's like you don't want to go advertising vulnerabilities before they're actually someone can do something, before the fix is out. Like, you know, hey, by the way, here's your bank account number. You should change it. I don't want to go publicizing that until you change your number, right? Right. And so that's that balancing act of working closely with the community, right, of knowing these folks of, hey, there's this vulnerability. How do we want to report it when good responsible CVE disclosure?
1:10:35and then we've, you know, from the overall Postgres project itself like we've got core developers just contributing back and just continuing to invest in those and have a set of folks on my staff that are we're paying them to work on Postgres and to make it better and contribute to it. That's good. So you do have ways. You know, what you just said there with the public nature of open sources is really I think the rub will hit on And I'm not trying to go back to that necessarily, but you were on that and made me think about that. So, you know, you said, can we share the issue? Well, that issue is public.
1:11:10The real challenge with open source today and the lens we take with it is that we think we, and maybe this is true when you read the licenses and the spirit of open source. And maybe I'm just not grounded enough. But you have open source. But does that mean that all the work that is open source has to happen in the public? and an example of security, the issues are public. So the discourse is public. And so the work is in the public. And so how do you have internal communications when everything is public? How do you have secure channels when all communications are in the public? And I feel like that's probably the tension and the change to come to open source is not so much, will we keep doing it?
1:11:54It's how do we conduct ourselves to do it? Because if the issues are in the public and you can't disclose, you have to have backchannels, well, now you're kind of circumventing the whole entire system, the whole entire workflow of what you think is work. I think Postgres, like, the source code is open, right? And, like, does the issue have to be, you know, like, maybe you publish it later, right? But it's like, you know, Postgres has had zero days in it. Not commonly, but in the last 15, 20 years, there's been about two zero days, right? And that meant, like, databases were publicly accessible.
1:12:28There's remote code exploits, privilege escalation. That's terrible. It just means your data is open. That is the worst thing that can happen to anything. Great. You can go read all the bank accounts, the private data. Your database being open to the world, just imagine that for anyone to come and grab. Bad day. Now, how do you resolve that? You've got to get the patch in. You've got to go do point releases. those point releases also have to be available on your provider right so as a community postgres has now got to go okay well who do we know at amazon who do we know at snowflake who do we know so that they can be ready on day one to go and roll their fleet not that oh post the new postgres is released well i wasn't expecting this it's it's you know uh about to be the fourth of july weekend i'm i'm i'm headed to the lake hang on like i don't want this like when do we release this?
1:13:23Are they ready for it so they can immediately patch? What if they have, you know, a week of downstream work once this hits, right? How do we keep our customers secure and work together, right? With all the people delivering Postgres and Postgres has done it really well, right? Like, and I think larger open source projects do do this, right? There's a way to do responsible disclosure. There's a way that they coordinate, you know, with, you know, key projects in upstream, right? If there's some core Ruby feature, that's a bug that needs to coordinate with Rails, they know how to do that from a Ruby to a Rails perspective.
1:13:58I think it's, you know, there's probably something for smaller projects to learn, but it's also like a point of scale, right? How do you, how do you scale that? Because it is, you do need those back channels, you need that coordination, but it does happen in Postgres and I don't think it's anti-open source. I don't think that, you know, the moment of vulnerability happens, it needs to be like for the world to be known, right? Yeah, we need to get it fixed and we need to do it in the best possible way. And there's a whole kind of aspect of like security, open source, and responsible disclosure that I think is, it's not that it wasn't important before, but man, AI has really amplified that importance, right?
1:14:42When anyone can find these vulnerabilities, right? Or if they know about them, take advantage of them, Just the risk there is higher than ever before. And so, you know, on that front, I'm not obviously an anthropic employee, clearly, right? I'm not high on the executive board there. I don't know what's going on behind the scenes when it comes to how they run their models. But I got to imagine that the usage patterns of someone doing cybersecurity things or nefarious things might look similar to a developer protecting themselves. But I bet they look a heck of a lot different. And so I think the way that you prompt the model, and so maybe they're using open source models, and maybe that's how they're getting around a lot of this.
1:15:25But, I mean, that's why Fable was so protected because of what you could do with it. I got to imagine, like, from the model level perspective, there's got to be things that you could do to detect how it's being prompted. And maybe that means you're prompt sniffing everything. I don't know. I mean, I don't know how to solve that conundrum there even on its own. But the usage of the developer or the builder or the operator, whatever you want to call them, prompting the model to get the results, whether it's in a orchestration system like Inductor or simply right in the CLI, whatever, right? There's a pattern that the person is doing to get the result back or to dig into something.
1:16:07I got to imagine that pattern is pretty clear for nefarious action. What do you think? Am I off on that? And maybe, except for like pulling that thread, it's like, well, if that pattern is clear, can I try to imitate someone that is like just a developer that's just trying to do like good local crypto and, you know, convince the model that's my path and then kind of keep pulling that thread to see if I can find something like, hey, is that a backdoor in, right? So, I mean, I don't envy their position, right? Like they want this to be available to people, but they've got a balance of like, you know, bad actors and what that means.
1:16:44And so I think at the surface, yeah, that makes sense. And then I start to pull that thread more and more. And well, okay, like where is the line? What's good? And as a bad actor, how can I make myself look like a good actor to then get as much out of the model as I can for my purposes, right? you know my and again i'm not coming back to this necessarily but like my fables back for one day you know uh i can't seem to get past anything security because i get so good at the security stuff i'm like well that's kind of what i want to ask you about you know i kind of want to ask you about like where is my application stack vulnerable fix it don't don't go and you know attack someone but fix it so i'm not attacked i don't understand that scenario but you know it's a different world we're in right now because they're trying to protect it so much i guess it's just that powerful um yeah it's just the nature of the beast in the moment i suppose yeah and i think you know well the pace these things are moving right like in a week we'll have a completely different conversation i'll be like you know what it's wide open like it's you know the the pace of change here and i think at first it was exhausting i think now i'm getting back to being fun it's like man okay like i'm back to the early days of learning to develop right and and building those first you know ruby apps and it's it's it's it's starting to feel fun again like at first it was overwhelming it's like man i don't have my creativity i can't learn like what what i'm just prompting like what's the but it's like actually no like now the limit is like your creativity and how far you can push things, which it's flipped for me that it's went from overwhelming to it's a fun time.
1:18:32And, but yeah, I hear you. It's like, man, I want to use this for like the good. Why is it constricting me? I think we'll be, you know, it'll continue to evolve for us. Yeah. Hopefully, because if not, we'll have to just, I think what will probably happen is that they'll just make fable or things that do that kind of stuff. Like, I'd even happily, like, give them, you know, more of my personal identification to prove I'm not a nefarious actor. Like, name it back to a real person. Am I literally a real ID, real kind of person that has a driver's license, that pays taxes, that, you know, is, you know, I got a utility bill.
1:19:12You know what I mean? Like, you got to do these certain things to get certain credentials or capabilities. Like, why not that? You know, maybe they'll do that sometime in the near future. I think. If not, we may have to go back to like manually writing code, right? I mean, like knowing stuff, we can't go back to that. Come on, man. Like I want to just like wish it into existence. That is just so much easier. To OpenAI's credit, I was doing something with a login. I was building a, you mentioned ETL earlier. I was building an ETL pipeline to move some data around. And I had to, let's just say, get access through just logging a password.
1:19:50I had to find my way in, let's just say. And opening, I was like, hey, this seems like you're doing things you probably shouldn't be doing here. And it flagged me. And I was like, oh, my gosh, I've never been flagged before because I'm just trying to help my sales team get access to data here and pull the data here, transform it, move it over there, all that good stuff, an ETL pipeline. and i'm like i'm hey hang on a second here i started defending myself like i'm just helping the sales team move data we have our data our leads over here we need to move them over there kind of thing and uh and to opening eyes credit they let you submit a form to apply to get that level of not like a certification but like you had to do yeah do something i forget what it was but it was enough to say i'm real i'm advocating that i'm trying to do things that are not nefarious you know don't flag me so much or flag me at all and there and ever since then nothing so i was kind of happy about that like i wouldn't mind a little of me to get a benefit it's like security clearance in a way it's good to know i did a similar um like family went to like disney world a little while back and like that like making those like dining reservations yeah it's like at like like man those things go like that and so i'm like all right this is just running for me locally.
1:21:08I want you to log in. There's no API for what availability is. I'm like, alright, I want to screen scrape and text me when there's this new reservation available for this restaurant because the kids want to eat Beauty and the Beast or whatever, right? And it's sold out. And then like, hey, it's not available. So I didn't get prompted and told, hey, you're doing something weird. So it was probably back before they had more control. So good to know. The next time I run into it i can just yeah fill out a form and uh and i'm pretty sure they even link to it in the air because i was like really i was concerned uh this is maybe like two months ago and i was like oh my gosh like that's the first time i had this stark feeling in my brain like what if they took your
1:21:54Craig Kerstiens: codex away from you adam what would you do then what would you like i'm just kidding you know i can't have stopped now i stopped now promise like that full panic of like uh-oh are they gonna I didn't mean it, Sam. Don't take my codex away. Anyways, I really did have a panic. I'm like, well, hang on a second. I'm not a terrorist. I'm not doing bad. And they had a link to the form. I filled it out. It's all been good since then.
1:22:23This episode is brought to you by our friends at Fingerprint. There's an interesting problem happening today. Building products. You want to make sure things are as easy as possible for your users. But you also need to know who or what you can trust. That's getting more complicated today with AI. AI agents are browsing, they're shopping, they're transacting alongside humans. Some of that automation is legitimate. Obviously, I use AI, you use AI, but some of it is not legitimate. And fraudsters, the bad guys, are getting more sophisticated. That's where fingerprint comes in. Fingerprint gives developers device intelligence to recognize returning visitors and make better trust decisions.
1:23:08It combines more than 100 signals across devices, networks, and behavior to identify visitors with precision, even as fraud tactics evolve. And it goes beyond identification. Fingerprint helps you detect bots, AI agents, proxies, VPNs, and other indicators of suspicious activity. So now you can protect accounts, prevent fraud, and reduce unnecessary friction for the people who actually use your product. And the developer experience is straightforward. One API call, no fraud detection model to build or to maintain. And now with AI install, you can add fingerprint to your platform directly from your favorite AI tool.
1:23:51So if you're building products for a world where humans and agents share the same internet, fingerprint is worth checking out. Head to fingerprint.com to get started. Once again, that's fingerprint.com.
1:24:12this episode is brought to you by work os agents aren't just writing code anymore they're accessing customer data they're taking actions across the tools we use and depend on so who decides what they're allowed to do that's a big theme from work os and knit 2026 their conference for builders they previewed three products that show where things are heading. First, Airlock, intent-based access control for AI agents. In a live demo, an agent worked across Linear, Snowflake, Stripe, and Gmail. Airlock denied a large refund, sent a smaller one to a human for approval, and blocked an email containing financial data.
1:24:51And then there's Atlas, a secure home for internal apps built with AI. Think authentication, data connections, credentials, permissions, and deployment. The stuff a prototype needs before it's safe to use at work. And then they have Passport. WorkOS is pushed towards zero sign-in. Enroll your Mac once, then open WorkApps already signed in. All three were announced as previous, but the direction is clear. As AI makes software easier to build, we need to get more serious about who and what can access it. I'm linking up the init 2026 recap. So check it out at workos.com. Link is in the show notes.
1:25:32Thanks again to our friends at workOS for sponsoring ChangeLog. Once again, workos.com. But man, wow. Okay. So Postgres 19, the future is Postgres. We've been Postgres for life for life. what is the next big thing to come in i don't know what do you predict for the next year so by december give me some predictions you got anything i mean i think a lot of what we're doing with pg lake is pretty it's early and new like i'll come back to it that it's like it sort of blows your mind at first like postgres shouldn't be doing this stuff i think you know ai plugging into Postgres, everyone's like, what's Postgres got to do with AI?
1:26:19It's like, well, it's the database that everyone's going to use under the covers, right? I think your point, like, how do we have kind of like database agents like optimizing our Postgres? Because most developers aren't great at it, right? But I think, you know, we covered a lot of it, like extensions, you know, Postgres 19, it's final, it's going to be in there, but it's not here yet. So I think that's the big thing, and development's already happening for 20. I think flexibility on data types, richness of text search, all those things just continue to get better. It's hard for me to say, oh, what's the big prediction?
1:27:00It's like, man, we're going to have some awesome new extensions come out that get released, and Postgres is going to keep getting better and more performant, and it's just going to be like, what's the prediction for my bank? Well, I hope it just keeps my money safe. and you know like yeah that's postgres is just gonna like keep you know keep doing what it does it's like a flywheel in a way right you know you have the core nugget which is good and then you have the the core nugget that has extensions and you can make things that make it better and those things make it better and then more things make the things make the things make it better the next thing you know you sort of have this multiplication happening in this flywheel happening as each layer matures.
1:27:41And like you had said, with, with PG Lake, you've got several components beneath it from table to engine to iceberg, you know, all the different components that make it up, all the different extensions to make a PG Lake, you know, that's, that's really interesting. And getting better at that is probably what will happen for Postgres at large. What about PG Lake? What's, what's a good way into PG Lake for someone? If someone's out there thinking, you know what i i've heard about this uh that sounds really cool uh yeah duck db and parquet sure that's awesome data analytics okay cool how does someone get involved with pg lake what can what can they do with it how do they add it to postgres yeah search pg lake and you it'll come up to github right you can install the extension yourself right you can pull it down locally kick the tires like it's available on snowflake postgres right you like like i don't want to build Postgres.
1:28:33I don't want to think about, like, how do I, like, it's on stuff like Postgres, so you can just run, you know, create extension pg-like, and boom, you've got it all there, right? And you can kick the tires, see how that works. But yeah, you can also contribute to it as well. I mean, hop over to GitHub, throw a star on it. Everyone loves a GitHub star. See what's going on with it. Like, it continues to get active development. We released it back in November, but it was actually, like, two years of work of development from back in our crunchy data days. so a lot of advanced engineering that then was open source two years later and we're continuing to invest in and you know shoot me a note Craig Kirstein's on on Twitter or I guess it's x now I can still Twitter to me always will be but it's x now um like send your feedback on what you'd like to see or you know hey have you thought about this like I you know the crazy ideas that people are like well have you you know consider this or this seems weird or crazy like I love it Let's go build it.
1:29:31What about Snowflake? What's on the, is PG like the edge for Snowflake? You know, in what ways is Snowflake truly adopting? And I know you mentioned developers being paid to invest in Postgres, but like what is Snowflake's big bet on Postgres? Yeah, so everyone that I think, you know, uses Snowflake also probably uses Postgres somewhere, right? And we talked about this a while ago of this divide of OLTP and OLAP and different kind of teams and systems and bridging those two together. For us, PGLake is sort of the foundation, but the end perfect result is what we recently announced, like database mirroring, where I can just run one command and mirror my Postgres database to Snowflake and vice versa.
1:30:20And not have to think about CVC, not have to think about ETL. It's literally like click a few buttons in a UI and the tables are continuously replicated in real time. And you don't have to think about it. You don't have to worry about it. So now you've got your transactional system. Your analytical system has the exact same data. Like I've got one customer that's a smart TV provider that ingests all this stuff real time into Postgres. So like, you know, you're viewing Disney Junior at home. I see you're in San Francisco. We're sending all this data into Postgres. Postgres now feeds that into, in this case, it's PG Lake.
1:30:57It could be mirroring. That snowflake picks up and does all this analysis. And it's like, okay, we see your viewing history. We see where you're located. Now we want to, because everything's an ad platform these days. So it's a smart TV. So we want to show some ads. We know Disney on ice is coming to Oakland next month. So we want to show this ad. So your kids are like, dad, please, can we go? It's right here. Can we go? and yeah I'm so annoyed at the ads on my TV because they're usually pretty accurate and good so Snowflake they used in Cortex Snowflake's kind of AI layer on top to then say what ads should we show that goes from Snowflake back to Postgres to be that real time single millisecond serving layer and it's like this is just common data pipeline now with like oh yeah I used Postgres before but now I want to tie it to my Snowflake experience And it's like, cool, there's a lot of beauty in the simplicity of these things I can build.
1:31:53For me, it's so, you know, I run databases. It's not cool. It's not the sexiest thing in the world. But like, I live vicariously through all these cool things people get to build. Like, you know, oh, cool, this makes sense on this like TV pipeline for advertising. I've got one customer that he surveys snakes in Canada. like goes out, catches snakes, tracks the population of them. So like two, three days of the week, he's out in the field catching snakes and tracking the population of them. And then he feeds this into a Postgres database using PostGIS. So like guy, part-time snake catcher, part-time like...
1:32:38Data collector, he's a censor. Yeah, it's like, I'm like, how do you eat? Like, what is this like job that you get? Like, this is cool. Like, I'd love to, like, go to the, you know, the job fair at the school and talk about, like, yeah, I catch snakes and I throw them in a database. And that's how I track all this and the population over time. Like, so for me, I get to live vicariously in all these, like, awesome apps and use cases people build. Right. And so at the core of it, like, Snowflake, absolutely amazing for analytics. and now we want to tie that together of like your perfect data platform for like analytics, AI, data all together.
1:33:18Yeah, I mean, I'm a home labber. I've recently changed to saying dev lab versus home lab just because my lab is now just so developer. I mean, it always has been, but like it's so developer. And it's almost like when you talk to an agent about home lab, it's kind of a pejorative in a way to them. like oh it's there's no scale there you're just doing toy stuff it's like no no you gotta do right you gotta do raspberry pies that's shut your mouth agent this is a developer lab man we're doing some cool stuff in here okay we're breaking ground we're innovating anyways i'm just thinking like any given decent dev lab sorry if you don't should have likely has a proxmox box which is a place you can you know it's a hypervisor you can stand up virtual machines and elixies and all that good stuff there uh you know i hadn't really paid much attention to pg lake it's about eight months old right this isn't a very old project maybe it's old in terms of development but not or old in terms of open source it's relatively new in the last year like it's basically a data warehouse in a box now and so why not stand up a virtual machine with some disk that's hardened Maybe you got TrueNAS you could back it up to and actually create a centralized data warehouse in your dev lab just for fun.
1:34:40Collect your data there. I'm looking forward to next time to hearing all the ways you analyzed your data with PG Lake. I'm going to. So I do a lot of stuff. Actually, I moonlight for fun, really for fun. A few folks of mine, I've helped them create some data pipelines, like ETL pipelines and stuff like that. And so I've got kind of a framework I built that, you know, uses Postgres, obviously, in some cases, but by and large, it's DuckDB and Parquet, right? I mean, especially whenever I'm extracting, extracting to a Parquet file with watermarking, like that is the way. It's fast. You can analyze it pretty quickly.
1:35:18You can even use a just file to kind of create a bespoke kind of like just-in-time API over the query. So rather than writing the queries all yourself, you just package them up in a just file, for example. and it kind of makes it like this kind of fairly quickly uh an ability to sort of like iterate over data at least it's where i've been playing at uh but i don't really have a centralized place to kind of keep all my data at once it's gotten there like that's the next big problem actually is like oh my gosh i have all this data how do i harden it okay i gotta actually centralize it it's not just one tenant it's several it's like two or three tenants so like the tenant have to be isolated.
1:35:58Like tenant one can't know about tenant two at all. It's just data. It's a warehouse to put it to. So this is my next problem really. And so maybe I'll stand up a VM on my product box box and become a DBA for PG Lake. There we go. We got one more, one more DBA in the world. I love it. One more. Yeah. One more for sure. Well, Craig, thank you so much, man. What else can we, you know, I know we mentioned PG Lake, how to get there, et cetera. anything coming from that that you can talk about that makes sense now? What else in closing can we talk about? That's a good question. I mean, I think the biggest, you know, the other thing is like, hey, you know, there's a lot of people like, where do I go to learn a little more about Postgres, right?
1:36:42Like, cool, this is exciting. How do I, you know, a few things. One, the Postgres mailing list. Like, man, you want to geek out on Postgres? The PG SQL hackers mailing list? that's where the development for Postgres happens like you want to go learn all in the public? All of it? I'm sure there's back channels but no the PG SQL hackers mailing list you want to learn about databases and get a master class it's a great spot you want to contribute and help others the PG SQL users mailing lists that's where users show up like hey I'm I've got this query and it's not performing. Go help someone else out.
1:37:28Helping others is a great thing. If you really want to get involved, look at the commit fest. See if you can go review a patch and contribute in that way. I think it's a small set of people and a huge thank you to actually commit and contribute to Postgres. This is open source in its truest, purest form. As an open source fan, I love it. I want to see it kind of thrive. It's 30 years old, and yet it's still going. And I can't think of any other things kind of like, man, what JavaScript framework has lasted more than two, right? Like we have a new one every so long. Man, give me back some jQuery.
1:38:12Is jQuery still around? It is still around. There's a version recently. Really? Like in the last year, yeah. There's a new release. Man, I want to go give jQuery a good old ride. But it's been a minute. But yeah, kudos to the Postgres committers. I'd love to see the community keep growing. And there's so many ways you can contribute, whether it's local user groups or if you want to learn more. I think because people here love learning, right? Go check out the hackers mailing list and have some fun. Don't be afraid of it. As soon as Postgres 19 is out in a couple of months, kick the tires, take a look at the new features.
1:38:51Like, don't be afraid of your database. I think most people are. They're like, oh, no, that's scary. That's hard. That's complicated. Like, we're developers. We're curious. Like, dig in. Like, Postgres doesn't have to be scary. That's my biggest kind of takeaway for folks is, like, dig in, have some fun with it, learn a little. And then if, you know, you find it exciting, contribute back in any small way that you can. Yeah. Yeah. The, you know, remind me how to get involved on mailing lists. I mean, so it's pgsql-hackers at postgresql.org. I'll tell you. Yes. And if you basically search for that, I think like you'll come up to, here's how you subscribe.
1:39:37There's more than mailing lists. There's multiple mailing lists, right? And so those are the two, I think, you know, the hackers one, which is where the actual development happens. and then the user ones for debugging. But there's one for like the dub, dub, dub and announcements and all sorts. So like go read the Postgres wiki on all the mailing lists. You know, if you're like, man, I don't want to know how the sausage is made, but I'd love to help. Like I'm good at this or that. Like there's maybe one for you there. Hey, one more question for you before I let you go. You know, I'm a small angel investor in Superbase and I've met some folks that are, I mean, I guess they're the futures version of developer, but they're certainly not a version of the past version of the developer that are now using Postgres.
1:40:22I'm like, what are you using Postgres for? And they're like, or sorry, they're not using Postgres. They are using Postgres, but they don't know they're using Postgres. Yeah. I'm like, what are you using for your database? Are they like Superbase? I'm like, no, that's not your database. That's where your database is. And I know now because they said Superbase, they're using Postgres, but they don't know. What do you think about this? Like, especially Superbase, they've had a major hockey stick with the influx and inflection point that we're in right now with database usage and stuff like that. Like having big players like PlanetScale and Superbase and Neon and a few others like choosing Postgres, this must have made like your career magnum opus.
1:40:58Like just the fact that like we're now here and when you choose a database, you're not actually, the developer of the future isn't choosing Postgres, they're choosing the thing that chose Postgres because they had good tastes. What do you think about that? Yeah, no, I think it's interesting to me because I see so many folks that are doing, like, you know, I love the Supabase folks. I love what PlanetScale is doing. Like, wait, DevCools are cool again, right? Like, man, we're back to Heroku and GitHub again. Finally, DevCools are cool again, right? Because for a while, we went through this phase.
1:41:29We're like, man, as an angel investor, do you really want to invest in DevTools? Like, that's throwing some money out the window for a little while, right? Supabase sounds like, shut up and take my money, man. Just take the money. Get it out of here. It's your money now, Superbase. Go do something with it. And I think Superbase for me is the closest parallel. It's Firebase. That's what they are. It's this easy layer for APIs and toolkits to build your app. More so than it is directly just a database provider. And so it's great that they're building on it. And there's other people that are like, oh, great.
1:42:03I'm going to go build my startup on Postgres or around Postgres or extend Postgres. and you know it's exciting I think to see that I'm also kind of amused a little bit that so many people are like man I know Postgres now and I'm the Postgres person and I've been in this space for two years and it's like man I feel like the old gray beard right like well I'm glad you come around because some of us have been doing this for a long long long time and yeah we have to be welcoming to the folks though you know we we do have to be welcoming I'm excited and more people means more software more software means more things that software does that just means there's just more right it's going to be i mean yeah i try to think about the negative but it's mostly net positive that i just keep coming back to like there's sure there's negatives but it's almost all net positives yeah i'm with you i think it's like but it's also like man building these products is hard right and doing this good is hard and so i think it's like there's a lot of value into doing this well right i think there are folks you know doing this really well like you've got to be solid it at the foundations, right?
1:43:07Like, I don't want the new kid out of college founding a bank and giving them my money, right? It's like, kind of want the institution that's been doing this for a few years. But a lot of those, I think, are pulling in core Postgres people, right? Like, they are really contributing back. And I think it's important when you look at all these, like, Postgres companies, you know, popping up, how much are they digging into the Postgres world, right? Are they becoming part of it? Or are they saying, hey, yeah, I'm throwing Postgres on my label because everyone loves Postgres. I think, you know, Supabase, PlanetScaler, too, that are really, like, good deep engineering and digging into Postgres.
1:43:45And I think there's, you know, you've just got to kind of, hey, are they really Postgres? Are they making Postgres better? Are they contributing back? It's an important evaluation for me because otherwise I think, like, that tide changes quickly and that foundation may not be there. yeah good word there good word there well Craig it's been a pleasure to catch back up with you again I always love talking about Postgres Postgres for life for life for life for life around here we need that shirt yeah we just need like endless for life's I don't know I feel like especially where we're at now it's not going to change for me you know I will say local dev I'm always with SQL Lite I've been dabbling with Tursle a little bit because why not but once it's prod or production like Postgres hardened, backed up, true etc can't why any other way and I definitely have to pay with PG Lake, I'm going to have to play with this anytime I'm happy to geek out on Postgres it's been too long, we'll do it again soon and yeah it doesn't take much to wind me up to geek out on Postgres for a little while.
1:44:59Right on. It's been super fun. Thanks for having me. It's good having you, Craig. Thank you. Well, friends, it's been the year of Postgres for many years now, but I think this year might actually be the year of Postgres. What do you think? Are you Postgres for life like I am? Maybe you're not. Who knows? But it's always good talking to Craig. He's always excited about Postgres, and I love that. Of course, a big thanks to our friends. over at fly.io the home of changelog.com and maybe the home of your agents learn more at fly.io of course the beat freaking residents break master cylinder bringing those beats not in our head and i love it let's get the show's done we'll see you in the next one
1:46:10Craig Kerstiens: Win it, win it. It really whips the.
Craig Kerstiens returns to talk about the ever-expanding world of Postgres: a deliberately boring core, a thriving extension ecosystem, and pg_lake bringing DuckDB and Iceberg into the mix. We dig into the pain of ETL, what Craig is watching in Postgres 19, the impact of AI on open source maintainers, and why the database still has plenty of room to grow.