1 00:00:02,130 --> 00:00:06,240 Claire Giordano: Hi, I'm Claire Giordano and welcome to Talking Postgres. 2 00:00:06,390 --> 00:00:09,330 Simon Willison: Biggest thing for me is that I never want to have to 3 00:00:09,330 --> 00:00:11,460 solve the same problem twice, ever. 4 00:00:11,490 --> 00:00:14,700 Claire Giordano: It's a podcast about the people who work with the Postgres 5 00:00:14,700 --> 00:00:17,040 database and why they do what they do. 6 00:00:17,125 --> 00:00:19,490 David Rowley: I think I get a similar little buzz out of speeding 7 00:00:19,490 --> 00:00:23,310 something up in Postgres as I did, maybe like, tuning my motorbike, or 8 00:00:23,310 --> 00:00:25,150 something, when I was in my twenties. 9 00:00:25,509 --> 00:00:29,049 Claire Giordano: You'll hear from Postgres people around the world: engineers, 10 00:00:29,110 --> 00:00:31,900 contributors, and curious users. 11 00:00:32,170 --> 00:00:36,100 And since I'm a bit obsessed with origin stories, we often dig 12 00:00:36,100 --> 00:00:37,810 into how people got their start. 13 00:00:38,230 --> 00:00:41,230 Tom Lane: Loved, and still love pinball, pool, bowling. 14 00:00:41,230 --> 00:00:43,410 Anything involving aiming at a target. 15 00:00:43,699 --> 00:00:46,390 I'm not any good at those things, mind you, but I love it. 16 00:00:46,629 --> 00:00:50,680 I just thought that the coolest job there could possibly be would be to design 17 00:00:50,680 --> 00:00:52,330 and build pinball machines for a living. 18 00:00:52,570 --> 00:00:55,675 Claire Giordano: What you'll love about these long form conversations 19 00:00:55,885 --> 00:01:00,835 is the backstage glimpse into the experiences of those who make Postgres 20 00:01:00,835 --> 00:01:06,025 happen both in the core database and across the broader ecosystem. 21 00:01:06,175 --> 00:01:07,765 Paul Ramsey: By a long shot, by a long shot. 22 00:01:07,765 --> 00:01:10,435 And it's an object lesson that everyone starts out writing a simple 23 00:01:10,435 --> 00:01:12,255 tool and then ends up writing a GIS. 24 00:01:12,304 --> 00:01:15,445 You just can't help it, you just keep adding, and adding, and adding, and before 25 00:01:15,445 --> 00:01:17,244 you know it, oh, I accidentally wrote a GIS. 26 00:01:17,365 --> 00:01:19,255 Shireesh Thota: It is open source at its best. 27 00:01:19,345 --> 00:01:23,355 I joke with everyone that it's the Linux of databases and it's amazing 28 00:01:23,355 --> 00:01:28,074 to have such a community who's very principled and forward looking. 29 00:01:28,124 --> 00:01:30,804 Dawn Wages: I think it's really easy to pick up Postgres because there's so 30 00:01:30,804 --> 00:01:33,354 many friends around who also use it. 31 00:01:33,535 --> 00:01:34,854 Claire Giordano: Nothing here is scripted. 32 00:01:35,180 --> 00:01:37,070 And it's not about speeds and feeds. 33 00:01:37,160 --> 00:01:42,440 Melanie Plageman: Over and over, I chose Postgres because I felt the values of 34 00:01:42,440 --> 00:01:47,340 the community, in terms of quality, and what they're trying to do, like, were 35 00:01:47,360 --> 00:01:49,400 really consistent with my personal values. 36 00:01:49,460 --> 00:01:53,390 Claire Giordano: It's about learning from the stories and experiences of others. 37 00:01:53,515 --> 00:01:54,565 Robert Haas: I just love that. 38 00:01:54,595 --> 00:01:59,335 Love the intellectual engagement of being able to discuss ideas about interesting 39 00:01:59,335 --> 00:02:03,715 topics with a bunch of other people who were really interested in that topic and 40 00:02:03,715 --> 00:02:05,905 had really clever things to say about it. 41 00:02:06,265 --> 00:02:09,565 Claire Giordano: A big part of the culture in open source is sharing what you know. 42 00:02:09,925 --> 00:02:13,315 So in each episode, guests talk candidly about what they've learned: 43 00:02:13,320 --> 00:02:17,715 Failures, wins, obstacles, and all the messy parts in between. 44 00:02:18,225 --> 00:02:21,315 Thomas Munro: There was a particular moment where we got some coverage and we got a lot 45 00:02:21,315 --> 00:02:26,415 of hits and our system completely melted down and we spent a couple of days figuring 46 00:02:26,415 --> 00:02:27,945 out what do we need to do to fix this? 47 00:02:27,945 --> 00:02:29,215 Like how can we handle more load? 48 00:02:29,445 --> 00:02:32,865 And that was kind of the beginning of a study of locking that led me to Postgres. 49 00:02:33,205 --> 00:02:36,675 Claire Giordano: If that sounds like your kind of podcast, check out Talking Postgres 50 00:02:37,035 --> 00:02:43,275 and subscribe on TalkingPostgres.com or wherever you get your podcasts.