1
00:00:05,300 --> 00:00:09,580
[CLAIRE] Welcome to Talking Postgres, a monthly podcast for developers who love this database.

2
00:00:10,160 --> 00:00:15,120
I'm your host, Claire Giordano, and in this podcast, we explore the human side of Postgres

3
00:00:15,420 --> 00:00:20,560
and databases and open source, which means why do people who work with Postgres do what

4
00:00:20,560 --> 00:00:22,300
they do and how did they get there?

5
00:00:22,780 --> 00:00:26,900
I want to say thank you to the team at Microsoft for sponsoring today's conversation.

6
00:00:27,720 --> 00:00:30,400
And today's guest is Melanie Plageman.

7
00:00:31,660 --> 00:00:38,040
Melanie is a Postgres committer, Postgres code contributor, works at Microsoft.

8
00:00:38,460 --> 00:00:40,900
She's actually, I think, technically a major contributor.

9
00:00:41,140 --> 00:00:44,180
There's different levels of official recognition there.

10
00:00:45,540 --> 00:00:49,040
Anyway, Melanie works at Microsoft on the Postgres open source contributor team.

11
00:00:49,520 --> 00:00:55,760
She's an organizer of the PGConf.dev conference on the talk selection team for POSETTE: An Event for Postgres

12
00:00:55,780 --> 00:01:00,420
and probably several other conferences that I'm overlooking right now.

13
00:01:01,350 --> 00:01:08,960
And I am thrilled that Melanie is here again because she has been a past guest on this

14
00:01:09,190 --> 00:01:14,340
podcast about a little bit more than a year ago, talking about her process of becoming

15
00:01:14,340 --> 00:01:15,300
a Postgres committer.

16
00:01:16,120 --> 00:01:16,280
Welcome.

17
00:01:17,340 --> 00:01:21,940
[MELANIE] Thanks, Claire. I'm happy that I could be here today and to talk about one of my favorite

18
00:01:22,260 --> 00:01:22,420
topics.

19
00:01:23,940 --> 00:01:27,500
[CLAIRE] Well, and so with that, we should probably tell people what the favorite topic is.

20
00:01:29,080 --> 00:01:35,660
So we decided to focus on PGConf.dev and specifically, I think the episode title is

21
00:01:35,660 --> 00:01:39,500
going to be what Postgres developers can expect from PGConf.dev.

22
00:01:39,900 --> 00:01:40,780
Does that sound right to you?

23
00:01:41,400 --> 00:01:42,080
[MELANIE] Yeah, totally.

24
00:01:43,520 --> 00:01:47,240
I can talk a little bit about PGConf.dev and what it is.

25
00:01:47,660 --> 00:01:48,180
Is that helpful?

26
00:01:48,820 --> 00:01:50,020
[CLAIRE] That is totally cool.

27
00:01:50,020 --> 00:01:54,680
I think people who haven't been will want your perspective.

28
00:01:54,840 --> 00:02:01,000
[MELANIE] Yeah, so it's timely because January 16th of next year is when the CFP closes.

29
00:02:02,760 --> 00:02:08,179
So this is sort of to give people an idea if you're not sure if you would want to go

30
00:02:08,220 --> 00:02:11,140
or be interested or get anything out of it, what it's about.

31
00:02:11,780 --> 00:02:15,820
So PGConf.dev has been in its current form going on for two years.

32
00:02:15,940 --> 00:02:18,760
But before that, there was a conference called PGCon.

33
00:02:21,260 --> 00:02:23,880
And Dan Langille organized it for years.

34
00:02:24,100 --> 00:02:26,020
I don't know how many years, but in Ottawa.

35
00:02:26,500 --> 00:02:27,400
Every year it was in Ottawa.

36
00:02:27,580 --> 00:02:35,620
And it was kind of like hackers got together and they, you know, talked about basically

37
00:02:36,040 --> 00:02:38,540
hacking Postgres and then also other community topics.

38
00:02:39,020 --> 00:02:48,080
But it was kind of like Dan organized it and there was pizza on Friday and it had

39
00:02:48,220 --> 00:02:50,620
that sort of informal hacker vibe,

40
00:02:51,200 --> 00:02:57,540
and I actually, that conference was really important to my development as a Postgres hacker because

41
00:02:58,180 --> 00:03:03,100
I had heard that it was awesome and that I should go and when I started hacking on Postgres like I

42
00:03:03,160 --> 00:03:08,800
was working at Greenplum and was interested in working more on upstream but didn't really know

43
00:03:09,060 --> 00:03:15,999
what I should work on or whether or not you know I didn't really have a direction yet and so I went

44
00:03:16,020 --> 00:03:23,180
And they used to, they have like a thing at the University of Ottawa where they rent out their dorms and you could pay like very little money.

45
00:03:23,430 --> 00:03:26,760
I don't remember what it was and have a shared room.

46
00:03:26,990 --> 00:03:31,240
You could have your own room too, but the cheapest is with someone you'd never met in a college dorm.

47
00:03:31,860 --> 00:03:33,420
So that was what I did the first year.

48
00:03:35,540 --> 00:03:42,460
And, you know, there's all these, you know, senior contributors that were there and you could talk to them and ask them questions.

49
00:03:43,200 --> 00:04:02,840
And, the first major feature that I worked on was an idea that Thomas Munro and Tomas Vondra were talking about this hash join feature and how to basically how to avoid this particular scenario.

50
00:04:03,480 --> 00:04:08,220
Or it was basically a bug that was tricky to fix and involved.

51
00:04:09,080 --> 00:04:12,340
The perfect solution was a big architectural change to hash join.

52
00:04:12,920 --> 00:04:14,580
And so I was like, okay, I'm going to do that.

53
00:04:15,120 --> 00:04:19,640
And it took me, I think, a year to even do the first version.

54
00:04:19,810 --> 00:04:22,620
I mean, not working on it continuously, but in my free time.

55
00:04:23,280 --> 00:04:27,700
And that was my first experience trying to write a major Postgres feature.

56
00:04:27,890 --> 00:04:32,700
And I never would have done it without having that in-person hallway track conversation.

57
00:04:33,340 --> 00:04:39,820
And I think PGCon was really like why, you know, one of the reasons why I'm a Postgres developer today.

58
00:04:39,960 --> 00:04:58,900
So when I heard from Jonathan [Katz] and other folks that they were thinking about transitioning the conference or that Dan was ready to focus on other things, I thought it's really important that this event continues because this is how we get new people.

59
00:04:59,120 --> 00:05:02,300
This is how they get inspired and motivated to actually stick around.

60
00:05:04,280 --> 00:05:11,680
So even though I did not want to do conference organizing at all, I agreed to try to help.

61
00:05:11,780 --> 00:05:13,260
And I'd never done it before.

62
00:05:14,000 --> 00:05:19,340
I think my closest brush with event organizing was organizing my wedding and I had a planner.

63
00:05:19,660 --> 00:05:27,580
So basically, I was completely out of my depth and had no idea what I was doing or what was required.

64
00:05:29,180 --> 00:05:30,920
[CLAIRE] I've seen pictures from your wedding.

65
00:05:31,040 --> 00:05:33,400
I was not there, but you have showed me some pictures,

66
00:05:33,520 --> 00:05:34,940
and it looked pretty darn awesome.

67
00:05:35,600 --> 00:05:38,480
So anybody who's getting married in the California Bay Area

68
00:05:38,680 --> 00:05:41,320
and needs a wedding planner, you should contact Melanie and get a tip.

69
00:05:42,300 --> 00:05:46,220
[MELANIE] Yeah, we got married in the Computer History Museum and had a hacking themed wedding and

70
00:05:46,220 --> 00:05:47,440
hackathon at the wedding, etc.

71
00:05:47,820 --> 00:05:55,459
So there was actually a surprising amount of overlap between that and the PGConf.dev

72
00:05:55,480 --> 00:06:03,540
event. So yeah, that's basically the background of how it came about. And it's still today,

73
00:06:05,060 --> 00:06:10,040
you know, a lot of the content is focused on Postgres development, but also extensions and

74
00:06:10,100 --> 00:06:14,840
the ecosystem and community building. We have all these people, wonderful people in the community

75
00:06:15,560 --> 00:06:20,280
that are making contributions other than code to the project. And they also need to get together

76
00:06:20,520 --> 00:06:25,440
and inspire each other and talk about what's not going well and come up with solutions for what

77
00:06:25,560 --> 00:06:42,480
They could do differently. And I think when, we, this new iteration of the event, one of our goals was to come up with different ways for people to interact, other than just relying on the people running into each other in the hallway and talking.

78
00:06:43,180 --> 00:07:11,100
So coming up with interactive content, you know, like workshops and panels and finding ways to take things that were happening, like the developer meeting, and democratizing access to it, creating these pathways and these sort of lanes for people who wouldn't necessarily just walk up to a senior contributor and start telling them their feature idea to actually interact with them.

79
00:07:11,560 --> 00:07:26,640
And then ways to create a sort of a corpus of material for teaching and, you know, I think introducing at least people to Postgres development and community organizing.

80
00:07:27,580 --> 00:07:39,500
And like, that's the reason why I still do it is that I think the opportunities to do the non-standard, not just a conference talk, right?

81
00:07:39,600 --> 00:07:44,920
Like getting to have these experimenting with these different types of content and having

82
00:07:44,970 --> 00:07:51,400
the goal just be like, let's get people to together and create environments where they

83
00:07:51,500 --> 00:07:57,340
can come up with new ideas and try new things and where we can get new people to, to want

84
00:07:57,340 --> 00:07:57,780
to stick around.

85
00:07:58,160 --> 00:07:59,920
That's a really interesting mandate.

86
00:08:00,080 --> 00:08:01,340
It's not a conference.

87
00:08:01,600 --> 00:08:03,680
It's a multimedia experience.

88
00:08:05,540 --> 00:08:06,100
So, yeah.

89
00:08:06,460 --> 00:08:06,800
[CLAIRE] I love it.

90
00:08:07,440 --> 00:08:08,900
Okay, so let's back up for a second.

91
00:08:09,000 --> 00:08:12,400
And I want to just get some facts on the table as I see them.

92
00:08:12,470 --> 00:08:13,900
And then you tell me what I'm missing.

93
00:08:14,540 --> 00:08:25,180
So the PGCon conference that you talked about that used to be in Ottawa transformed or morphed into PGConf.dev is what it's now called.

94
00:08:25,680 --> 00:08:33,440
And you're currently planning the third year of PGConf.dev since that cutover or migration, if you will.

95
00:08:33,820 --> 00:08:36,140
The first year it was in Vancouver.

96
00:08:36,150 --> 00:08:38,620
Last year or earlier this year in 2025.

97
00:08:38,640 --> 00:08:45,500
It happens in May. It was in Montreal. And in 2026, it's going to be back in Vancouver.

98
00:08:47,340 --> 00:08:54,980
There are about, I don't know, 200-ish people there, although I'm assuming you're planning for growth in 2026.

99
00:08:56,370 --> 00:08:57,440
Correct me if I'm wrong.

100
00:08:58,000 --> 00:09:05,399
[MELANIE] It's interesting we in after the first year we you know we sold out the conference and so we said

101
00:09:05,420 --> 00:09:11,500
okay, we're probably going to grow in the second year. And then we didn't, and the

102
00:09:11,880 --> 00:09:17,400
attendance didn't grow. So that's, that changes as a conference, you have to figure out which

103
00:09:17,640 --> 00:09:22,120
direction you're going. If you don't think you're going to grow attendance, either, you know, you

104
00:09:22,380 --> 00:09:27,240
can devote your time coming up with strategies to grow attendance, which I think has merit, right?

105
00:09:27,820 --> 00:09:32,720
Or you can say, okay, given our budget and the number of people we can expect to come,

106
00:09:32,800 --> 00:09:36,880
How can we make this experience as enriching as possible for those people?

107
00:09:37,620 --> 00:09:39,300
And we've kind of taken that strategy.

108
00:09:39,430 --> 00:09:41,840
So it's not that we don't want new people to come to it.

109
00:09:42,160 --> 00:09:44,580
It's just that there's only so much time.

110
00:09:44,740 --> 00:09:45,380
We're all volunteers.

111
00:09:45,730 --> 00:09:50,420
So we decided to focus less on, you know, we're still reaching out to people.

112
00:09:50,490 --> 00:09:55,040
We're going to post flyers on college campuses, but we're not planning for massive growth

113
00:09:55,480 --> 00:09:55,780
right now.

114
00:09:56,020 --> 00:09:56,120
[CLAIRE] Okay.

115
00:09:56,220 --> 00:10:05,480
Well, and that's kind of why I was envisioning that it will grow, because I know that you're planning on reaching out to college professors and flyers on campus.

116
00:10:05,940 --> 00:10:23,200
And I imagine for a student who has taken maybe a grad student or someone who's taken a bunch of database classes, even as an undergrad, if they found out about this, if they knew about it, particularly if one of their professors nudged them to go, I think they would just get a lot out of it.

117
00:10:23,260 --> 00:10:29,400
I know that the senior contributors, right, the existing community members get a lot out of it.

118
00:10:29,430 --> 00:10:33,640
Like people absolutely love this conference as an attendee.

119
00:10:34,240 --> 00:10:43,620
But I also think that folks who are new would find it welcoming and would find that mix between introductory content and more advanced content.

120
00:10:43,900 --> 00:10:48,900
I think you have a spectrum of possibilities for people.

121
00:10:49,600 --> 00:10:52,500
[MELANIE] Yeah, it's interesting because we do try to have beginner-friendly content.

122
00:10:55,580 --> 00:11:01,560
And I would say that it's just very hard to, so we've had it in the past. We had an intro to

123
00:11:01,700 --> 00:11:07,900
hacking workshop, an intro to how community development works, workshop. And you talk to

124
00:11:07,980 --> 00:11:14,140
people after and you say, you know, what did you get out of that? And what we at least saw in the

125
00:11:14,220 --> 00:11:20,239
year that we did that was we didn't get much conversions. Like, and we also didn't have people

126
00:11:20,300 --> 00:11:26,520
say we had one or two people say that was good. I enjoyed that. But it wasn't a resounding success.

127
00:11:27,220 --> 00:11:34,220
So we were like, okay, maybe people don't want an instructional workshop at this event. Maybe

128
00:11:34,380 --> 00:11:41,660
what they need is more opportunities to interact with people and get inspired. So not directly

129
00:11:41,850 --> 00:11:48,240
like instructional. So I would say that like, well, we do strive to have beginner friendly content.

130
00:11:48,440 --> 00:12:00,240
I think we're trying to find ways to interact with people that are new to the community that makes it most likely that they'll feel welcome and actually, you know, stick around.

131
00:12:00,430 --> 00:12:15,460
And maybe later, they, you know, engage with educational content and there's resources like Andrey Borodin's, I don't know if he's still doing the YouTube series, but where people review patches live and there's Robert's hacking workshop thing.

132
00:12:15,560 --> 00:12:25,320
And what we've found so far is that pure educational initiatives or extremely beginner friendly content isn't always very popular at the event.

133
00:12:25,840 --> 00:12:28,080
So that's one thing that we're trying.

134
00:12:28,320 --> 00:12:29,960
And we would love more feedback about this.

135
00:12:30,440 --> 00:12:36,800
And a lot of times beginners will say, well, I want to go to the really advanced stuff because I want to be like, you know, drinking from a fire hose.

136
00:12:36,920 --> 00:12:38,140
That's what I want out of this conference.

137
00:12:38,510 --> 00:12:40,100
So we're trying to figure out the right balance.

138
00:12:42,420 --> 00:12:42,840
[CLAIRE] At the end of the

139
00:12:42,920 --> 00:12:47,340
day, people are all different. So if you find the right balance for someone, then it's, it's,

140
00:12:47,740 --> 00:12:52,740
you know, you're, it's hard. It's, you can't meet everybody's needs, I suppose. But it sounds like

141
00:12:52,790 --> 00:12:58,100
you're trying to meet as many people's as possible within this developer community.

142
00:12:58,279 --> 00:13:03,100
[MELANIE] And for conferences, you deal with a pretty limited amount of feedback.

143
00:13:03,290 --> 00:13:06,420
Like we were really lucky because you did that unconference session where we got a lot

144
00:13:06,470 --> 00:13:06,840
of feedback.

145
00:13:06,990 --> 00:13:07,480
That was great.

146
00:13:08,130 --> 00:13:10,140
We did have a lot of people fill out the survey.

147
00:13:12,180 --> 00:13:17,600
For an individual piece of content, you're usually relying on only a couple pieces of feedback,

148
00:13:17,940 --> 00:13:22,840
right? So we've been pivoting hard every time we got feedback that was like, maybe you should do

149
00:13:22,980 --> 00:13:28,060
something else. And maybe that's not enough. Maybe you need to do it for multiple years to see the

150
00:13:28,260 --> 00:13:33,840
results. I'm not really sure. I think my tendency as soon as I get feedback is to try something

151
00:13:34,100 --> 00:13:37,200
totally different, right? And maybe that's not the right strategy. I don't know.

152
00:13:38,220 --> 00:13:43,260
[CLAIRE] So let's talk about the structure of the conference really quickly, because you just mentioned the unconference.

153
00:13:43,420 --> 00:13:50,940
But before we dive into that, Tuesday is usually some kind of pre-conference day.

154
00:13:51,020 --> 00:13:55,220
In the past, maybe there have been that's when the developer meeting happened last year.

155
00:13:55,380 --> 00:13:58,080
That's when the community summit happened, the extension summit happened.

156
00:13:58,560 --> 00:14:00,840
And I know Tuesday is going to be different this year.

157
00:14:00,970 --> 00:14:02,780
And we should talk about that in a little bit, too.

158
00:14:03,320 --> 00:14:13,240
Wednesday and Thursday have historically been the more traditional conference days with a keynote speaker and a bunch of other speakers and sessions.

159
00:14:13,940 --> 00:14:27,800
But you also had a community booth and you experimented with things that were, you know, more interactive types of things, where people could sign up to have someone, I don't know, help them.

160
00:14:28,900 --> 00:14:30,840
Well, you can explain that to us in a minute.

161
00:14:31,140 --> 00:14:33,080
And then Friday is the unconference day.

162
00:14:33,680 --> 00:14:34,680
And that's super cool.

163
00:14:35,040 --> 00:14:42,820
And every as far as I can tell, everybody stays for the unconference day, even though you don't know what the schedule is until you make it that morning,

164
00:14:43,100 --> 00:14:43,200
right?

165
00:14:43,280 --> 00:14:51,860
So it's kind of it can be a three day event for people who skip the Tuesday or for many people, it's a four day event.

166
00:14:52,070 --> 00:14:53,300
Is that a good overview?

167
00:14:54,260 --> 00:14:57,900
[MELANIE] Yeah, I would say this year, Tuesday is a full.

168
00:14:59,430 --> 00:15:02,300
So previously you had to pre-register for Tuesday's events.

169
00:15:02,660 --> 00:15:05,980
And basically, if you didn't register, you couldn't wait enough food.

170
00:15:06,140 --> 00:15:09,260
We didn't, you know, we weren't, it was a smaller day in terms of number of people.

171
00:15:09,800 --> 00:15:14,500
But what we decided to do this year is it's completely, it's open to anyone.

172
00:15:14,720 --> 00:15:15,180
Anyone can come.

173
00:15:15,180 --> 00:15:16,500
You don't need to sign up for anything in advance.

174
00:15:17,320 --> 00:15:22,320
And all of the, we're going to have enough content and enough stuff going on that everyone

175
00:15:22,360 --> 00:15:23,040
can find something.

176
00:15:23,180 --> 00:15:24,420
So it's a full day of the conference.

177
00:15:26,060 --> 00:15:30,700
The format will be different than the longer summits that we did last year.

178
00:15:30,800 --> 00:15:38,720
Instead, we're splitting it up into one hour or up to two hours, depending on it, like what we're calling community discussion sessions.

179
00:15:39,660 --> 00:15:59,920
And so it's kind of a day to take specific issues that you have, you know, whether it's something you want to change about the development process or you want to talk about, you know, the tools we're using or you want to talk about how the contributors recognition process can be different.

180
00:16:00,040 --> 00:16:06,060
Like some sort of issue that you want to meet with people and talk about that.

181
00:16:06,210 --> 00:16:12,580
Or it can be something, you know, within the ecosystem, like changes to the protocol and things like that.

182
00:16:13,060 --> 00:16:17,580
And so you suggest a session through the regular CFP.

183
00:16:18,270 --> 00:16:27,480
And then what you can sort of say, OK, this is there are certain people that we need at this meeting for it to be productive.

184
00:16:27,650 --> 00:16:29,760
Right. Like if, you know, Chris

185
00:16:30,020 --> 00:16:35,540
Ellis and Boriss don't agree to come to this meeting, we might as well not have it. And that's

186
00:16:35,800 --> 00:16:40,700
basically just to say, you know, sometimes what you find in these small group breakouts is that,

187
00:16:40,730 --> 00:16:45,340
oh, hey, we don't have anyone here who actually works on this. So there's no point in having this

188
00:16:45,430 --> 00:16:50,200
meeting, right? So in the community discussion sessions, you specify who would have to be at

189
00:16:50,200 --> 00:16:57,299
the meeting to make it productive. And then the rough, like, size that you think would make sense

190
00:16:57,320 --> 00:16:58,400
to allow into the meeting.

191
00:16:58,640 --> 00:17:00,120
So if you say, okay,

192
00:17:00,780 --> 00:17:02,620
if more than 30 people are in the session,

193
00:17:02,890 --> 00:17:05,160
it's gonna be too difficult

194
00:17:05,300 --> 00:17:06,240
to have a discussion, right?

195
00:17:06,620 --> 00:17:08,760
So then we'll put them in small rooms

196
00:17:08,959 --> 00:17:11,760
and anyone can attend unless you mark it as private,

197
00:17:12,060 --> 00:17:14,180
which is the security team might need to do that

198
00:17:14,180 --> 00:17:15,420
and have a private meeting, right?

199
00:17:15,959 --> 00:17:17,900
And so people that are attending Tuesday

200
00:17:18,280 --> 00:17:19,620
can wander into a session.

201
00:17:19,900 --> 00:17:21,500
Maybe they don't know anything

202
00:17:21,959 --> 00:17:23,339
about the Postgres protocol

203
00:17:23,819 --> 00:17:25,499
or they don't know anything about

204
00:17:25,520 --> 00:17:32,400
you know, how, what Psycopg and JDBC need from core, like, but they can learn about it and hear

205
00:17:32,580 --> 00:17:37,940
people who are working on those topics directly talk about it. And in that way, it has some

206
00:17:38,180 --> 00:17:43,380
similarities to the unconference, but it's all proposed ahead of time and people prepare material,

207
00:17:43,860 --> 00:17:49,419
that kind of thing. So it's a way to democratize content like the developer meeting, which was

208
00:17:49,440 --> 00:17:58,740
historically on Tuesday at PGConf.dev and make it so that also that people can go to more topics

209
00:17:58,950 --> 00:18:05,120
so that they can, you know, if they're interested in a particular topic, they can go to be part of

210
00:18:05,260 --> 00:18:09,980
that topic discussion and then switch. So you're not dedicated to a three-hour meeting where you

211
00:18:09,990 --> 00:18:15,399
only care about one topic. So it's a combination of wanting to democratize access and also free up

212
00:18:15,420 --> 00:18:20,540
people's time to be in more concurrent sessions. So all of that is happening. And then we also have

213
00:18:20,820 --> 00:18:25,500
another thing that's happening, which is, let's say 100 people at the conference are like, I don't

214
00:18:25,540 --> 00:18:30,720
want to go to a meeting about any of these topics. Well, we're going to do what we call the large

215
00:18:30,880 --> 00:18:37,280
room track with entertainment kind of content that's more focused on panels. Basically, it'll

216
00:18:37,280 --> 00:18:42,960
be almost all panels. And these are going to be things like, we still have to go through the CFP

217
00:18:43,580 --> 00:18:50,800
process, but imagine getting to pitch your Postgres feature idea to a group of committers

218
00:18:51,220 --> 00:18:56,620
or having senior contributors talk about the biggest mistakes they've made or whatever.

219
00:18:56,820 --> 00:19:02,780
We're going to have panels that highlight or imagine hearing conference organizers talk

220
00:19:02,780 --> 00:19:10,119
about how you can get involved. So have content that spotlights community members and things

221
00:19:10,160 --> 00:19:15,520
that they're doing, efforts they're doing in the community, and that's accessible to anyone.

222
00:19:15,650 --> 00:19:19,600
So it's sort of that beginner-friendly thing, but then it also might be interesting

223
00:19:19,650 --> 00:19:20,560
to experienced people.

224
00:19:23,400 --> 00:19:30,360
[CLAIRE] When I look at the CFP page, which I either just shared or I'm about to share in the Discord,

225
00:19:30,840 --> 00:19:34,000
and we'll be sure to put it in the show notes when we publish this episode,

226
00:19:34,600 --> 00:19:37,940
it looks like there are for the community discussion sessions.

227
00:19:38,460 --> 00:19:42,120
So there's CFP info all about talks you can submit, right?

228
00:19:42,660 --> 00:19:46,560
And then for community discussion sessions, there's the open discussion sessions.

229
00:19:46,840 --> 00:19:49,400
That's what you just talked about a few minutes ago, right?

230
00:19:49,820 --> 00:19:54,300
where you have required attendees and then anybody else can be in the audience and kind of

231
00:19:55,100 --> 00:19:57,220
be a fly on the wall right um and then I see the closed sessions you talked about that example the

232
00:20:00,800 --> 00:20:05,620
security group um working groups did you cover that one?

233
00:20:06,599 --> 00:20:14,900
[MELANIE] So that one is basically that you would you would have that it would be limited to a certain

234
00:20:15,160 --> 00:20:19,080
number of attendees above the ones that you mentioned.

235
00:20:20,300 --> 00:20:29,940
So the idea there is that maybe it's kind of like that invite only structure that the developer meeting had.

236
00:20:30,070 --> 00:20:41,980
If there's something where you feel like it would be productive to have the discussion be limited, because the people that you specifically specify are going to be the people presenting or talking or having discussion,

237
00:20:42,110 --> 00:20:47,360
right. But if you think that there needs to be other, it's halfway in between open and closed, if that makes sense.

238
00:20:48,020 --> 00:20:50,260
[CLAIRE] Okay, got it. And then there's this more, I don't know if entertainment's the right word,

239
00:20:54,940 --> 00:20:59,540
because then when you said that, I imagine people getting up there with their guitars or,

240
00:20:59,880 --> 00:21:03,520
you know what I mean, music, but the panel discussions that people

241
00:21:04,020 --> 00:21:08,340
can learn from and that'll be inspiring. And that's a fourth category, if you will.

242
00:21:08,400 --> 00:21:16,940
[MELANIE] Yes. Oh, and the other thing about working groups and open discussion. So an open discussion will be more like an unconference session where people can raise their hands and ask questions and weigh in, even if they're not

243
00:21:19,940 --> 00:21:24,800
one of the people that's sort of prepared for the meeting ahead of time and is a key attendee

244
00:21:25,160 --> 00:21:31,920
the working group will be basically if you attend and you're not one of the key people like it's more

245
00:21:32,020 --> 00:21:36,580
like your fly on the wall kind of thing and the open discussion is a bit more like the unconference

246
00:21:37,100 --> 00:21:42,460
and then you're right entertainment is probably not the right word but I think we realized

247
00:21:42,620 --> 00:21:49,800
with these community discussion sessions that it there would be people who were especially maybe

248
00:21:49,820 --> 00:21:59,680
if you're just getting started out in the Postgres community, maybe taking a step back and not being expected to participate in something,

249
00:21:59,780 --> 00:22:08,820
right. That can be intimidating to jump into a meeting of experienced Postgres community organizers and a small group setting,

250
00:22:09,220 --> 00:22:18,520
right. And if each if we have 200 people and we have three concurrent sessions, you don't want, you know, like 60 people in a meeting.

251
00:22:19,000 --> 00:22:26,840
So this is sort of the idea is like once the rooms are at capacity, then everybody else can go and have another way of connecting with the community.

252
00:22:29,160 --> 00:22:37,480
[CLAIRE] So when I think about the target audience for PGConf.dev, I see three classes of people.

253
00:22:37,680 --> 00:22:41,100
And tell me if I'm wrong, because you know this way better than I do.

254
00:22:41,580 --> 00:22:49,020
I mean, obviously, the first class of people are existing Postgres contributors, committers.

255
00:22:50,140 --> 00:22:54,060
They can be code contributors or they can be other kinds of contributors like me.

256
00:22:54,750 --> 00:22:56,180
So that's that's one class.

257
00:22:56,840 --> 00:23:06,840
Another class are people who are perhaps new to Postgres, new to Postgres as a contributor, as a developer, as a user.

258
00:23:07,440 --> 00:23:11,620
And they're just there to figure out, like, do they have a future?

259
00:23:11,670 --> 00:23:14,820
Do they want a future working on this project?

260
00:23:16,580 --> 00:23:20,940
The third class of people are and I have seen Postgres users who attend,

261
00:23:21,450 --> 00:23:21,660
right.

262
00:23:21,770 --> 00:23:23,480
They're not contributors today.

263
00:23:23,610 --> 00:23:27,300
And maybe they don't want to be beyond filing of bugs,

264
00:23:27,720 --> 00:23:27,820
right.

265
00:23:28,820 --> 00:23:34,299
But they still there's a lot of value to be had by attending sessions and learning about

266
00:23:34,360 --> 00:23:39,260
different aspects of particularly the new releases and some of the new features.

267
00:23:40,260 --> 00:23:41,420
Those are the three buckets.

268
00:23:41,580 --> 00:23:45,640
Did I miss anything?

269
00:23:43,600 --> 00:23:47,680
[MELANIE] I think there's one, I don't know if this falls in, but like, you know, maintainers

270
00:23:47,700 --> 00:23:54,720
of ecosystem projects. So drivers and extensions, they have things that they need

271
00:23:54,720 --> 00:23:59,260
to talk about in a group. And there isn't really another event that caters to that.

272
00:23:59,510 --> 00:24:03,620
And then they also have things that they would like to talk about with core developers.

273
00:24:05,740 --> 00:24:11,860
And so I think that's sort of another category. And with the users, like you were

274
00:24:12,000 --> 00:24:16,980
saying, I think there are also advanced users who are like, this is a persistent problem

275
00:24:17,000 --> 00:24:22,240
that I'm having. It's not a specific bug, but Postgres architecture or something, you know,

276
00:24:22,460 --> 00:24:28,300
sort of in Postgres needs to change because these are the modern use cases. These are things that

277
00:24:28,300 --> 00:24:34,800
we're seeing, you know, in the field, basically. And if it's not a bug, we might not hear about it,

278
00:24:34,940 --> 00:24:38,980
right? So seeing those patterns, hearing from advanced users about how they're using

279
00:24:39,320 --> 00:24:41,420
Postgres is really important.

280
00:24:42,420 --> 00:24:51,200
[CLAIRE] Which brings up this word that if you haven't attended Postgres conferences or other tech conferences before, maybe you're not familiar with the term hallway track.

281
00:24:51,900 --> 00:24:57,780
But the hallway track at PGConf.dev is incredibly vibrant and energetic.

282
00:24:58,220 --> 00:25:04,700
And I at least feel like I could walk up to anybody, introduce myself, talk to them.

283
00:25:05,620 --> 00:25:19,740
And so, yeah, there is that ability for a user to go introduce themselves to somebody who is a committer, is a contributor and might have an opinion or some ability to influence the future of Postgres.

284
00:25:21,300 --> 00:25:23,400
[MELANIE] Not everyone feels comfortable doing that so another thing that's one of our core

285
00:25:25,960 --> 00:25:32,820
goals is to kind of create opportunities to break apart cliques of people that already know each

286
00:25:32,840 --> 00:25:40,620
other and infuse other people into it, so we're doing a um like a novice or you know new to

287
00:25:40,640 --> 00:25:47,180
Postgres breakfast where people that either haven't been to a conference before or are new to using

288
00:25:47,380 --> 00:25:51,020
Postgres or maybe there's new to Postgres conferences will come and then experienced

289
00:25:51,260 --> 00:25:55,620
community people will be there in a small group setting where they can all talk. We're doing last

290
00:25:55,620 --> 00:26:00,340
year we did something or this year we did something called the meet and eat where you sign up and one

291
00:26:00,360 --> 00:26:06,320
of the nights you get put in a small group and we specifically tried to mix together experienced and

292
00:26:06,320 --> 00:26:12,840
new people into groups and you go out to eat to dinner with those people.

293
00:26:13,120 --> 00:26:19,120
[CLAIRE] And can we pause on that for a second, what was really cool about that is once you sign up

294
00:26:18,760 --> 00:26:23,840
then you get assigned to a group of people and the group of people like mine was like eight or nine

295
00:26:24,180 --> 00:26:30,000
right so mine wasn't a crazy big group um but it was big enough that there were there were definitely

296
00:26:30,240 --> 00:26:36,320
interesting people to talk to and what I like about it is you don't have to figure out

297
00:26:36,640 --> 00:26:39,240
how do I get invited to one of these dinners or you don't have to find the right person who would

298
00:26:42,820 --> 00:26:48,880
invite you, you know. It's the structure is there and it's provided by the organizers by you

299
00:26:48,880 --> 00:26:52,100
guys and uh it was really nice. I liked it.

300
00:26:53,320 --> 00:26:57,340
[MELANIE] Also usually at a conference when you're all standing around trying to figure out where

301
00:26:57,400 --> 00:27:01,120
you're going to go to dinner you have a group of 20 people that suddenly are like we need to go

302
00:27:01,300 --> 00:27:05,580
somewhere and we don't have a reservation so I was like maybe we can solve both these problems

303
00:27:05,810 --> 00:27:11,280
which is actually being able to go somewhere and get enough seats and everyone eat and you know

304
00:27:11,490 --> 00:27:16,240
getting some mixing so we're going to do it on two nights this year instead of one um because there's

305
00:27:16,260 --> 00:27:21,200
the night that traditionally like if your company has enough people there and they're doing a dinner

306
00:27:21,740 --> 00:27:26,800
that means all the people that are not doing that are sort of left to their own devices. So we're

307
00:27:26,800 --> 00:27:31,740
going to do a second meet and eat for for that night as well so we're like really trying to fill

308
00:27:31,920 --> 00:27:37,580
in the spaces. Obviously you still want time for people that are going there to like, I go and there

309
00:27:37,580 --> 00:27:43,040
are people that I work with only online that I only see once a year at this event right so I

310
00:27:43,060 --> 00:27:48,040
obviously want time to talk to them, catch up on like, you know, how's your new house? Like,

311
00:27:48,140 --> 00:27:53,020
what are you up to? And, you know, sort of have like private one-on-one conversations with them

312
00:27:53,380 --> 00:27:59,580
and talk about ideas and what we're working on. But like, I think we can allow those spaces while

313
00:27:59,880 --> 00:28:06,740
also trying to fill in as much space as we can with getting people together and pushing them out

314
00:28:06,740 --> 00:28:11,440
of their comfort zone, right? Like, I think a lot of this event is pushing people who are used to

315
00:28:11,460 --> 00:28:15,420
going to these events and hanging out with the same people out of their comfort zone.

316
00:28:16,060 --> 00:28:17,880
But like you get something for it, right?

317
00:28:17,940 --> 00:28:19,640
You get to go to a restaurant with a reservation.

318
00:28:20,220 --> 00:28:24,040
So like even if you would rather maybe hang out with the two people that you are, it's

319
00:28:24,280 --> 00:28:24,860
obviously optional.

320
00:28:25,000 --> 00:28:31,160
But that's sort of like we're trying to create value by giving people new experiences

321
00:28:31,320 --> 00:28:34,540
and that benefits people who already know people as well as new people.

322
00:28:36,000 --> 00:28:48,740
[CLAIRE] Well, and the timing of PGConf.dev in May, I guess I can't read Dan Langille's mind to know why May was selected way back in the day, many, many years ago when it was PGCon.

323
00:28:49,380 --> 00:28:55,620
But the timing is pretty perfect for kicking off the development cycle for the next release of Postgres.

324
00:28:56,200 --> 00:29:02,460
So by the time you get there in May, PG 19 code freeze will have already happened, right?

325
00:29:03,300 --> 00:29:05,600
And because that happens in the beginning of April.

326
00:29:06,320 --> 00:29:12,480
And so it'll be time to start working on, oh my gosh, Postgres 20.

327
00:29:12,730 --> 00:29:13,320
Is that right?

328
00:29:13,340 --> 00:29:15,640
[MELANIE] Yeah, yeah, yeah, yeah.

329
00:29:16,380 --> 00:29:18,880
No, it's a really important time of year for reconnecting and coming up with ideas for the

330
00:29:23,160 --> 00:29:24,040
next release, right?

331
00:29:24,720 --> 00:29:30,600
So one thing that happens at other developer meetings, like the FOSDEM developer meeting,

332
00:29:30,920 --> 00:29:35,840
they spend time looking at, okay, what patches are still out there that like, we need to figure

333
00:29:36,040 --> 00:29:41,920
out if they're going to go in or not go in or whatever. It's more tactical and specific. But

334
00:29:42,240 --> 00:29:47,820
at PGConf.dev, like, it's that breath between releases, obviously, we're still stabilizing the,

335
00:29:48,260 --> 00:29:54,180
you know, we'll still be stabilizing 19. But we like, there's all the crazy ideas can come out,

336
00:29:54,340 --> 00:30:00,240
right? We can be like, what if we did multi threading, or, you know, and that, that kind of

337
00:30:00,260 --> 00:30:08,060
stuff maybe it starts on the list but like momentum and that at the um PGConf.dev this year like the

338
00:30:08,420 --> 00:30:12,540
multi-threading people were like we should actually make a working group and and commit to action items

339
00:30:12,960 --> 00:30:19,580
you know that kind of thing um and so it's kind of like uh it's easy if you said you were going

340
00:30:19,580 --> 00:30:24,000
to do something but you never see the people asynchronously to kind of just ignore that

341
00:30:24,240 --> 00:30:30,220
thread on hackers but if you see everybody in person it kind of is like oh yeah that is

342
00:30:30,240 --> 00:30:34,980
to me, I do want to make sure and do that and coming up with ideas. And so in the development

343
00:30:35,320 --> 00:30:39,920
calendar, it's at a particularly also like, what features slipped the release, and it made me sad,

344
00:30:40,080 --> 00:30:44,720
like, it's just this time that it's kind of like any, it's almost like a launch party, I want to

345
00:30:44,900 --> 00:30:48,060
say, like, even though it's not really launching, because we don't have anything like that in the

346
00:30:48,220 --> 00:30:52,200
community, right? We don't do parties when a new release of Postgres comes out. So it's kind of

347
00:30:53,080 --> 00:31:00,180
like that time where you do the things you might do in a traditional like project that

348
00:31:01,140 --> 00:31:07,280
that to celebrate to mourn you know to to get together and figure out what's next and

349
00:31:07,610 --> 00:31:12,260
I think it works for non-code contributions too like you know what do we want to do differently

350
00:31:12,350 --> 00:31:17,080
in the next development year also works for non-code contributions.

351
00:31:18,900 --> 00:31:23,160
[CLAIRE] I worked the hallway track last year looking for future podcast guests, right?

352
00:31:23,400 --> 00:31:28,380
Getting people's ideas about what episodes really resonated with them and who else do

353
00:31:28,380 --> 00:31:29,320
they want to hear from.

354
00:31:29,740 --> 00:31:33,940
And I got a whole bunch of good ideas from people who were there.

355
00:31:34,640 --> 00:31:37,380
I have this quote in front of me that's actually from you, Melanie.

356
00:31:38,080 --> 00:31:43,440
And it was from the trip report that I wrote internally at Microsoft after going to PGConf.dev

357
00:31:43,560 --> 00:31:44,260
last year.

358
00:31:44,560 --> 00:31:46,080
And it wasn't just my trip report.

359
00:31:46,260 --> 00:31:51,760
I was trying to represent like our whole team of open source contributors for Postgres.

360
00:31:51,920 --> 00:31:53,460
And I just want to read it out loud.

361
00:31:53,760 --> 00:31:54,840
I hope it's not too long.

362
00:31:55,580 --> 00:31:59,100
Those of you on the Discord chat, let me know if it was worth it or not.

363
00:31:59,280 --> 00:32:03,940
But you told me, PGConf.dev is at the end of the development year and an opportunity

364
00:32:04,460 --> 00:32:10,160
for us to reconvene, reflect on our missteps and feel less alone when sharing those missteps

365
00:32:10,500 --> 00:32:13,380
and get excited about what we're going to work on in the next year.

366
00:32:13,980 --> 00:32:28,480
It's a chance to find out how everyone is doing and to connect on a human level, to find people who are interested in the projects we want to work on in the next year and convince other people who are planning to get in the way of those projects to reconsider.

367
00:32:29,320 --> 00:32:34,960
It's a giant mix of negotiating, celebrating, planning, mourning, educating, and inspiring.

368
00:32:37,220 --> 00:32:37,960
You said that.

369
00:32:38,480 --> 00:32:42,020
[MELANIE] Yeah, well, that sounds better than my rambling just now.

370
00:32:43,100 --> 00:32:56,700
[CLAIRE] They're both good. They're both good. I just like that mix of negotiating and celebration and planning and mourning. I mean, there are all those dichotomies and different sides of different coins that are happening together.

371
00:32:57,360 --> 00:32:59,740
[MELANIE] And we don't have another venue for that, right?

372
00:32:59,880 --> 00:33:01,300
Like when else would we all do that?

373
00:33:01,320 --> 00:33:03,600
You can't really do that stuff remotely.

374
00:33:04,260 --> 00:33:06,140
Like how would you, you know, do that?

375
00:33:06,200 --> 00:33:11,820
It wouldn't, I mean, some of it may be tactical specific stuff, but it's an emotional

376
00:33:12,040 --> 00:33:12,480
thing, right?

377
00:33:13,080 --> 00:33:32,580
[CLAIRE] So on the chat, Boriss Mejías asked a few minutes ago if you could help him understand the difference between, say, PGConf New York City, which is a very, I think, user-centric conference, although it has a lot of committers and contributors who were there as well and who are speakers typically.

378
00:33:33,500 --> 00:33:35,900
PGConf New York City versus PGConf.dev.

379
00:33:37,540 --> 00:33:38,200
People understand.

380
00:33:38,610 --> 00:33:40,280
[MELANIE] Yeah. I think Tristan's answer is good.

381
00:33:40,420 --> 00:33:47,940
And basically, yeah, every other Postgres conference is more user-focused.

382
00:33:48,280 --> 00:33:57,080
But I think there's actually a distinction that I like even more because there might be content from users at our conference.

383
00:33:57,580 --> 00:34:00,880
It's that other conferences are more outward-facing.

384
00:34:02,240 --> 00:34:05,400
I know, PGConf.EU did do a community day.

385
00:34:05,460 --> 00:34:10,300
But this conference is about the people making Postgres and the Postgres community.

386
00:34:10,360 --> 00:34:15,840
So everyone is welcome but they're welcome with the idea that like you're gonna do work right

387
00:34:16,300 --> 00:34:22,879
you're not there to uh you're there in your I guess you're there in the role of like

388
00:34:23,379 --> 00:34:27,659
contributing to the community so if you contribute by just talking about how you use Postgres

389
00:34:28,100 --> 00:34:34,860
that's okay too but the whole point of it is it's it's like for the community internally to try to

390
00:34:35,020 --> 00:34:39,220
make ourselves better it's like a community development sort of like if you have a retreat

391
00:34:39,220 --> 00:34:43,020
for work or whatever, where you're like, let's all connect more. Let's figure out what's next.

392
00:34:43,740 --> 00:34:48,800
It's that. It's not to try to convince more people to use Postgres. It's to try to figure

393
00:34:48,850 --> 00:34:56,460
out how we can make Postgres better.

394
00:34:51,520 --> 00:34:53,840
[CLAIRE] So nobody's selling Postgres at this conference.

395
00:34:53,960 --> 00:34:55,960
And oh, there are no booths.

396
00:34:56,480 --> 00:34:57,720
So people sponsor.

397
00:34:58,500 --> 00:35:00,680
Microsoft is going to be a sponsor this year.

398
00:35:02,020 --> 00:35:06,500
Some of the other hyperscalers and Postgres companies are too, of course,

399
00:35:07,020 --> 00:35:13,340
because we know that this collaboration that happens at this event has to be funded somehow, right?

400
00:35:14,540 --> 00:35:16,460
So companies step up.

401
00:35:17,040 --> 00:35:23,140
But companies don't get a direct transactional benefit from the sponsorship at this conference.

402
00:35:23,210 --> 00:35:23,980
There are no booths.

403
00:35:24,040 --> 00:35:24,740
There are no scans.

404
00:35:25,520 --> 00:35:33,520
There are no, there's no sign that we get to put up, as far as I know, that, you know, advertises our Postgres, you know, database services.

405
00:35:34,220 --> 00:35:44,340
But the benefit we get is, of course, the fact that it contributes to the health and the future of this community of people who work on the project.

406
00:35:45,090 --> 00:35:55,240
And anybody who's in the business of Postgres, and there are a lot of companies, I mean, I think Postgres is a it's a multibillion dollar industry.

407
00:35:55,940 --> 00:36:00,500
And anyone who's in that business knows that you've got to support the upstream project.

408
00:36:01,240 --> 00:36:05,160
You have to fertilize it, nurture it, grow it, invest in it.

409
00:36:05,340 --> 00:36:07,820
And that's part of what sponsoring PGConf.dev gets you.

410
00:36:08,280 --> 00:36:13,660
[MELANIE] Yeah, and I I tell people it's like would your office cancel the yearly project planning

411
00:36:13,830 --> 00:36:18,020
meeting where you decide your roadmap like it's not that simple because there's no roadmap right

412
00:36:18,140 --> 00:36:24,220
it's an open source project and we we do you know that's what's great about it. It's chaotic and it's

413
00:36:24,240 --> 00:36:31,940
it's not some, it's not top down, but on some level, we don't have any other project

414
00:36:32,320 --> 00:36:36,200
planning meeting, right? Like we don't have any other discussion where we're all in person.

415
00:36:36,380 --> 00:36:42,440
There's nothing. So like, why would you as a company that relies on Postgres not sponsor

416
00:36:42,720 --> 00:36:48,240
the event? That's the closest thing to that happening, you know? So, yeah.

417
00:36:48,480 --> 00:36:54,200
[CLAIRE] Yeah. So if you're listening and you don't know if your company, your business, your project is a sponsor yet, you should go.

418
00:36:55,960 --> 00:37:02,360
I'll make sure in the show notes to include the sponsorship link. And so you could you could look into that.

419
00:37:02,360 --> 00:37:05,780
And of course, there's different levels. And I'm not meaning this to be a sales pitch.

420
00:37:06,540 --> 00:37:11,680
I'm I first of all, I'm not part of the organizing team for PGConf.dev.

421
00:37:12,080 --> 00:37:13,700
I'm not on the talk selection team.

422
00:37:14,200 --> 00:37:19,240
I will volunteer as we get closer and I like to take pictures of speakers.

423
00:37:19,360 --> 00:37:21,120
So that's probably the way in which I'll volunteer.

424
00:37:21,500 --> 00:37:24,120
Oh, you're hiring a photographer this year for one of the days, though.

425
00:37:24,280 --> 00:37:43,320
[MELANIE] Yes. Okay. Wait, before we keep going, because I know some people might drop at two, I wanted to answer Boriss's question about, or two things that he said on the chat. So one of them was he mentioned the debates they did at PG Day Lowlands. And I did, so I talked to Derk about this because I thought that was a really interesting format.

426
00:37:33,320 --> 00:37:33,800
[CLAIRE] Okay,

427
00:37:44,100 --> 00:37:44,760
Derk van Veen.

428
00:37:44,960 --> 00:38:00,520
[MELANIE] Yeah, and we discussed like if so he can't come to PGConf.dev, he said, but because we're in the CFP process right now. So anything like that debate idea would have to go through the normal CFP. That's kind of how we're trying to make it fair, even for content that we're kind of soliciting.

429
00:38:01,560 --> 00:38:15,320
And so if someone from PG Day Lowlands or someone else, but preferably because they actually have experience having done it and know what worked and didn't work, wants to propose that, we would be interested in doing the debate.

430
00:38:15,380 --> 00:38:27,300
Because I think it's a really interesting, you know, idea, which is like you have instead of a panel, you have kind of like your high school debate team take for and against a particular idea positions,

431
00:38:27,460 --> 00:38:29,580
and then you have to like argue for them.

432
00:38:30,120 --> 00:38:33,040
So things that we're very interested in

433
00:38:33,160 --> 00:38:34,900
and we would love to see proposals.

434
00:38:35,070 --> 00:38:38,120
Like we also have a category, which is other ideas, right?

435
00:38:38,060 --> 00:38:39,740
So do you have an other idea?

436
00:38:40,000 --> 00:38:41,540
Like last year, one of our most,

437
00:38:42,370 --> 00:38:43,380
or this year, sorry, 2025,

438
00:38:44,060 --> 00:38:46,560
the new thing that we did that was very popular

439
00:38:46,920 --> 00:38:47,900
was poster sessions.

440
00:38:48,070 --> 00:38:49,740
So Andrey Borodin organized this.

441
00:38:50,160 --> 00:38:52,300
He is an academic and like said,

442
00:38:52,460 --> 00:38:54,900
you know, in academia, we have these posters

443
00:38:55,110 --> 00:38:56,579
and we put them up and then people can

444
00:38:56,600 --> 00:39:02,040
like look at what projects people are working on and it doesn't have to be a whole talk session

445
00:39:03,160 --> 00:39:08,540
and people loved them and we are uh we're good we're doing it again but we're making it even

446
00:39:08,720 --> 00:39:13,520
bigger so even if you don't attend the conference you you know if you can't make it you can have a

447
00:39:13,640 --> 00:39:18,340
poster for your project or your initiative or whatever um we'll print them out we're going to

448
00:39:18,500 --> 00:39:23,120
feature them and we're going to have time where people can go and talk to the poster uh like

449
00:39:23,140 --> 00:39:26,320
owner, they'll stand by their poster if they're there and you could ask them questions

450
00:39:27,220 --> 00:39:32,200
and so that's something that we've got great feedback about and we're like okay let's blow

451
00:39:32,250 --> 00:39:41,180
this up and make it bigger and a bigger part of the event.

452
00:39:34,900 --> 00:39:39,600
[CLAIRE] Is there going to be a separate call for posters or what's the timing on that?

453
00:39:41,270 --> 00:39:46,980
[MELANIE] Yes, yes. That'll happen after the main CFP closes and they all go on the website too so last year's all the pictures of all the

454
00:39:46,660 --> 00:39:53,100
posters are on the 2025 website and the 2026 will go on the website too and so it's a great way if

455
00:39:53,120 --> 00:39:57,040
going to be there and you want to you know talk about something you're doing or like it's also

456
00:39:57,320 --> 00:40:01,000
for if you have a patch and no one's paying attention to it or like it's kind of this

457
00:40:01,960 --> 00:40:08,060
um you know this way to get people engaged with their content um so that's a new thing that we're

458
00:40:08,180 --> 00:40:16,620
doing and uh there's like other things like we do a run um like a you know Yurii [Rashkovskii] organizes a run where

459
00:40:16,840 --> 00:40:23,080
he plans a route and and you can walk or whatever pace you run and go on that and like any

460
00:40:23,100 --> 00:40:29,300
new ideas for different types of content and like ways to engage we're looking for that so

461
00:40:29,300 --> 00:40:33,540
you can submit anything that's just like an other ideas category so you could submit it to there.

462
00:40:34,760 --> 00:40:35,200
[CLAIRE] I love it.

463
00:40:36,200 --> 00:40:42,300
[MELANIE] And the other thing that was asked was about anniversary celebrations of Postgres so um [Drum roll, drum roll, drum roll.]

464
00:40:45,280 --> 00:40:48,760
yeah so 30 years of the open source project, 40 years of the Postgres

465
00:40:48,840 --> 00:40:51,280
like code base or you know [Technology.] yeah technology uh so there may be some other community anniversary

466
00:40:57,480 --> 00:41:01,480
celebration like I know there are people that are talking about it working on it whatever but that

467
00:41:01,580 --> 00:41:09,580
we are definitely going to do things to celebrate it at this event so for example um we are this is

468
00:41:09,740 --> 00:41:14,560
still in development like but we're trying to or and we're not having a traditional keynote or

469
00:41:15,580 --> 00:41:20,940
we're planning on having some of the original people that were involved in the open source project

470
00:41:21,660 --> 00:41:26,700
talk and that's where we're still, I think we're still ironing out the details but I think

471
00:41:26,940 --> 00:41:34,480
like it to honor the anniversary we want to make sure that there is a spotlight on some of the

472
00:41:34,600 --> 00:41:38,240
people in the community that were there at the very beginning so that's why I was saying like

473
00:41:38,440 --> 00:41:43,000
you mentioned the photographer, I want to have someone come and take high quality pictures of

474
00:41:43,600 --> 00:41:48,380
all of the, you know, the people that have been in the community for a long time and everybody

475
00:41:48,580 --> 00:41:52,140
that's new, right? Like we have this amazing journey. Tomas Vondra is going to put together

476
00:41:52,680 --> 00:41:59,560
a massive slideshow of pictures from the past 30 years all the way up until today. Like last week,

477
00:41:59,780 --> 00:42:06,560
the Nairobi PUG, the new Nairobi PUG had its first meeting. Like we have this huge journey with this

478
00:42:06,980 --> 00:42:12,460
giant global community. So if you have photos that you want to share and have in the slideshow,

479
00:42:12,640 --> 00:42:17,580
send them to Tomas Vondra. We're going to project it either on the wall or have it on a screen.

480
00:42:18,340 --> 00:42:24,260
We're also working on special stuff like special swag for the anniversary and then

481
00:42:24,650 --> 00:42:29,340
other opportunities to sort of commemorate and engage with it. So it's a lot of TBD,

482
00:42:29,430 --> 00:42:31,300
but we're definitely going to be highlighting it.

483
00:42:33,820 --> 00:42:38,660
[CLAIRE] One of the things that I think is really important for the Postgres community, and I know that

484
00:42:38,740 --> 00:42:45,260
the committers and the core team and the major contributors are all probably talking about this,

485
00:42:45,480 --> 00:42:51,580
thinking about this, like planning for the future, not in a roadmap sort of way, but in a, hey,

486
00:42:52,120 --> 00:43:00,020
over time, eventually some people are going to move on or retire. And so I love the fact that

487
00:43:00,780 --> 00:43:07,220
everything you're talking about for PGConf.dev, yes, it will help Postgres 20, right? It will help

488
00:43:07,240 --> 00:43:12,100
the next release. It will help the existing contributors and committers. But I love the

489
00:43:12,100 --> 00:43:17,620
fact that you're also looking at how can you like democratize access and make all this information

490
00:43:18,420 --> 00:43:24,220
available, accessible, inspiring to what will effectively become the next generation of open

491
00:43:24,400 --> 00:43:34,700
source contributors. And I think that's important. And you know that because I like that's one of the

492
00:43:33,760 --> 00:43:38,680
goals for this podcast, right? It's unstated. You don't find it when you go to talkingpostgres.com

493
00:43:38,820 --> 00:43:43,640
and you look at the episodes. It doesn't say that our goal is to nurture the next generation

494
00:43:44,160 --> 00:43:48,300
of open source contributors and committers, but that is one of the unstated goals.

495
00:43:48,940 --> 00:43:55,980
Like, I want this to be interesting to you, Melanie, and to other, you know, Postgres contributors

496
00:43:56,480 --> 00:44:01,560
and users, but also to people who are just getting involved, to give them that peek behind the

497
00:44:01,580 --> 00:44:02,380
curtains, if you will.

498
00:44:02,640 --> 00:44:11,860
[MELANIE] And there's, I think there's a lot of people that are, you know, in the ecosystem, they're working on a project that is related to Postgres.

499
00:44:12,420 --> 00:44:19,700
And we haven't, like, quite sucked them into the main Postgres community and got them involved in event organizing.

500
00:44:19,760 --> 00:44:22,440
And there's all these app developers, right, that are using Postgres.

501
00:44:22,600 --> 00:44:29,520
And, like, they also could have a voice and add value to the direction of Postgres.

502
00:44:29,980 --> 00:44:38,000
So like when talking about expanding, I think, you know, the event, we do want even more perspectives.

503
00:44:38,500 --> 00:44:46,980
Right. So one thing that we're like, as we're talking about the CFP, if you're like, well, I'm not a Postgres developer and not a conference organizer.

504
00:44:47,880 --> 00:44:51,700
Like, could I submit a talk? You totally can.

505
00:44:52,560 --> 00:44:58,160
So like I mentioned that we want the perspective of so you just think of it from the perspective of like, I'm a user.

506
00:44:58,440 --> 00:45:01,940
So here are things that I wish would be different about Postgres.

507
00:45:02,180 --> 00:45:06,780
So as you're thinking about your talk proposal, thinking about how to frame it so

508
00:45:06,920 --> 00:45:10,040
that it's about making Postgres or making Postgres community.

509
00:45:10,500 --> 00:45:14,420
There are people that have, you know, submitted talks about like, I think this process should

510
00:45:14,660 --> 00:45:19,460
exist in the community for recognizing contributors, or I think we should have a foundation or

511
00:45:19,560 --> 00:45:20,440
I think, you know, whatever,

512
00:45:21,480 --> 00:45:31,200
like the angle of your talk is like this is what post the Postgres project like needs to be or this

513
00:45:31,200 --> 00:45:35,580
is my idea for what I think it should how it should be or how it should be different or how it could

514
00:45:35,580 --> 00:45:41,960
be better right and um those perspectives are really important like I think Chris just mentioned

515
00:45:42,140 --> 00:45:47,880
that not you know app devs don't always feel comfortable submitting um but like if the

516
00:45:47,900 --> 00:45:53,580
conference was just feature ideas in a vacuum and it's you know Thomas Munro talking and Heikki

517
00:45:53,720 --> 00:45:59,620
talking about multi-threading and then uh you know me and Andres or whoever talking about obscure

518
00:45:59,820 --> 00:46:06,780
performance issues like then it's not it it becomes insular right like if we don't if we're not like

519
00:46:07,140 --> 00:46:13,359
other conferences have user concerns in them but if we're not also hearing about what users need

520
00:46:13,780 --> 00:46:17,580
to change in Postgres, then we won't actually do it.

521
00:46:17,820 --> 00:46:25,080
Not everyone is reading pgsql-hackers or going to send an idea to the mailing list that

522
00:46:25,300 --> 00:46:27,220
doesn't come with the patch because that's often discouraged.

523
00:46:27,920 --> 00:46:30,120
So I think it is a venue for that.

524
00:46:30,160 --> 00:46:34,820
And if we don't have that, then it has less value because how are developers going to

525
00:46:35,320 --> 00:46:37,200
know what to make?

526
00:46:40,460 --> 00:46:46,060
[CLAIRE] What's interesting is this notion of imposter syndrome to me it's something that so many people

527
00:46:46,320 --> 00:46:52,060
feel a lot of people don't say it out loud a lot of people don't admit to it but it's just so easy

528
00:46:52,470 --> 00:46:58,040
to feel that way and to hear Chris talk about you know not feeling quite comfortable pitching a talk

529
00:46:58,060 --> 00:47:06,480
for a PGConf.dev. Chris is brilliant. He has so much insight to share about how he uses Postgres

530
00:47:06,560 --> 00:47:14,040
and what he needs and stories to tell about failures and successes and requirements. And like,

531
00:47:14,700 --> 00:47:19,520
if Chris can't submit a talk proposal, I don't know. It's just, it boggles my mind sometimes.

532
00:47:20,520 --> 00:47:26,580
[MELANIE] Yeah I definitely want to know what we can do to make it feel accessible like

533
00:47:28,600 --> 00:47:35,800
I like I don't want like I think some group like there are some let me think okay Linux

534
00:47:35,820 --> 00:47:40,600
Plumbers conference is an example of another conference that is sort of has this it's content

535
00:47:40,690 --> 00:47:46,400
about making Linux right and I haven't been but like because I think it's invite only but my

536
00:47:46,660 --> 00:47:49,720
understanding of it is it's like, it's very, you know, like it would be very intimidating for a

537
00:47:55,300 --> 00:48:01,240
Linux user to go even if it was open right but like we want to have some of the aspects of what

538
00:48:01,260 --> 00:48:06,640
happens at conferences like that, which is productive forward work towards like features

539
00:48:06,810 --> 00:48:10,660
and solving systemic like developer quality of life stuff, right?

540
00:48:10,830 --> 00:48:12,540
For us as Postgres hackers.

541
00:48:13,070 --> 00:48:16,780
But that is only half the picture, right?

542
00:48:16,960 --> 00:48:24,240
I would be really sad if our event was something that, like I just said, doesn't have the perspective

543
00:48:24,280 --> 00:48:29,640
of Postgres community organizers and, you know, app developers and users.

544
00:48:29,890 --> 00:48:32,660
And like, because we would be missing that.

545
00:48:32,660 --> 00:48:34,460
This conference has these two purposes.

546
00:48:34,770 --> 00:48:40,020
I mean, I guess three, if you consider growing new people, like one of its purposes is to

547
00:48:40,170 --> 00:48:43,500
figure out how to move forward on new work in the database.

548
00:48:44,030 --> 00:48:47,380
But another is to figure out what should we be working on?

549
00:48:47,480 --> 00:48:54,240
And you don't get that without other perspectives.

550
00:48:54,820 --> 00:48:58,160
[CLAIRE] Letting that sink in for people, hence the blank space.

551
00:48:59,120 --> 00:49:14,420
Okay, so if you're listening and you want to attend and you work, like some people work for a boss or for a company where they just tell their boss, I want to attend and it's all paid for and no business justification needed.

552
00:49:15,000 --> 00:49:15,500
That's cool.

553
00:49:16,100 --> 00:49:25,200
But some people need to write up a paragraph of business justification in order to get their bosses support to attend and to travel.

554
00:49:25,440 --> 00:49:28,800
And maybe they have to get a visa and fill out some forms and things like that.

555
00:49:29,280 --> 00:49:39,060
So for me, what I wrote up last year in this trip report that I mentioned a few minutes ago, as I wrote, it's where the next release begins.

556
00:49:39,820 --> 00:49:41,780
It's where decisions get made for the project.

557
00:49:42,440 --> 00:49:45,020
It's where the next generation of contributors is nurtured.

558
00:49:45,780 --> 00:49:48,800
it's where our Postgres contributors refuel and reconnect.

559
00:49:49,520 --> 00:49:51,100
And I just wrote down those four points,

560
00:49:51,500 --> 00:49:53,480
but you're mentioning even more points than that.

561
00:49:54,080 --> 00:49:54,220
So...

562
00:49:54,840 --> 00:50:01,320
[MELANIE] And we also have a travel grant this year so um there's an application um if you go to attend on

563
00:50:01,320 --> 00:50:06,840
the website and then click travel grant it describes it and has an application but uh it

564
00:50:07,480 --> 00:50:14,800
for people that are like you sort of have to have the intent to contribute to Postgres or be

565
00:50:15,080 --> 00:50:20,440
contributing like one of those things uh to be eligible for it but the idea is like not everyone's

566
00:50:20,460 --> 00:50:26,440
employer is going to pay for them to go. So it covers hotel and the conference ticket. And then

567
00:50:26,480 --> 00:50:33,000
in some cases we can cover flights, but it's the idea is that like, we want it to be accessible.

568
00:50:33,300 --> 00:50:39,340
I think also, I don't know if people notice, but the price of the conference is much lower than

569
00:50:39,600 --> 00:50:46,440
last year. So our 2026 will be 350 Canadian and it used to be 500 Canadian. So we are,

570
00:50:47,180 --> 00:51:08,120
As soon as we got sponsorship dollars, we were like, what can we do to make the conference accessible? How can we make it so that more people can come to the event? So we have the travel grant, the ticket prices, we've lowered the ticket prices. So we're really trying to make it something that more people can attend.

571
00:51:09,580 --> 00:51:15,460
[CLAIRE] The location is Simon Fraser University, which I guess the acronym is SFU.

572
00:51:15,480 --> 00:51:16,040
Is that right?

573
00:51:16,420 --> 00:51:18,240
And it's it's right in Vancouver.

574
00:51:18,380 --> 00:51:20,260
So there's a ton of nearby hotels.

575
00:51:20,780 --> 00:51:25,560
I mean, I know some people prefer Airbnbs, but for me, I stay at Marriott.

576
00:51:25,560 --> 00:51:29,820
So there's a whole bunch of Marriotts in the area, walking distance even from this.

577
00:51:30,080 --> 00:51:31,020
Lots of coffee shops nearby.

578
00:51:31,960 --> 00:51:36,160
[MELANIE] And one of the things is Vancouver is more expensive for hotels, you know, it's not cheap.

579
00:51:36,300 --> 00:51:45,780
So I think in our hotel blocks, like having the travel grant for that should take away one of the big barriers to attendance, we think.

580
00:51:45,820 --> 00:51:54,880
um so it's much easier to get like if you are an accepted speaker then the travel grant is like

581
00:51:56,100 --> 00:52:00,100
i won't say it's guaranteed but like it's much more likely if your employer can't pay for you

582
00:52:00,680 --> 00:52:04,280
um if you're not an accepted speaker you can still make a case for like

583
00:52:04,910 --> 00:52:09,840
what you are going to what you are or are going to bring to the Postgres community and how you're

584
00:52:09,860 --> 00:52:15,980
going to contribute. Yeah, you should, you should do that.

585
00:52:10,660 --> 00:52:14,140
[CLAIRE] Obviously if your employer can pay for you to go that's the way to do it,

586
00:52:17,080 --> 00:52:21,440
well because that way you have the funds available for people who really really need it [Yes.]

587
00:52:21,240 --> 00:52:29,360
and for people who are going to have to say no or not not attend um so yeah so I know there's so

588
00:52:29,380 --> 00:52:36,540
much more to talk about with PGConf.dev, but I also want to ask you about other talk selection

589
00:52:36,880 --> 00:52:54,360
teams that you might be serving on. Are there any?

590
00:52:39,700 --> 00:52:51,760
[MELANIE] Yeah. Yeah. Claire, who has made the POSETTE CFP deadline the same as PGConf.dev.

591
00:52:55,000 --> 00:52:57,920
[CLAIRE] No, I haven't. [No, isn't it January 16th?] No, no. The POSETTE, February 1st, Sunday, February 1st, which is the Sunday of FOSDEM. [Oh.]

592
00:52:59,440 --> 00:53:02,820
So at FOSDEM, I'll be able to work the hallways or work

593
00:53:03,160 --> 00:53:07,840
the college campus in Brussels, making sure people remember and don't miss the deadline.

594
00:53:08,240 --> 00:53:13,080
[MELANIE] Oh, you're right. Okay. I just checked. Okay.

595
00:53:10,480 --> 00:53:12,460
[CLAIRE] Yeah, I wouldn't do that to you.

596
00:53:14,420 --> 00:53:16,940
I don't want to compete with PGConf.dev at all.

597
00:53:17,170 --> 00:53:19,040
And of course, because that's totally different, right?

598
00:53:19,560 --> 00:53:23,640
No, it's a virtual event happening for the fifth year.

599
00:53:24,080 --> 00:53:27,960
And anyway, Melanie is serving on this talk selection team.

600
00:53:28,140 --> 00:53:34,120
And I know it's a lot of work because last year I think we had 240 talk proposals.

601
00:53:34,620 --> 00:53:37,280
So it's a lot to review all these proposals.

602
00:53:37,700 --> 00:53:41,400
I feel like your, obviously your PGConf.dev work is even bigger

603
00:53:41,700 --> 00:53:45,580
and even more than that in the sense that you are both an organizer

604
00:53:45,900 --> 00:53:49,200
and on the talk selection team for PGConf.dev, right?

605
00:53:49,180 --> 00:53:49,820
[MELANIE] It's a lot of work.

606
00:53:51,060 --> 00:53:53,420
[CLAIRE] That's a ton of work, which is high impact.

607
00:53:54,040 --> 00:54:08,300
I know at Microsoft, all of our rewards and promotions and things are all tied up with this concept of impact and, you know, finding ways to shine a light on what, how have you changed?

608
00:54:08,640 --> 00:54:14,880
Have you changed things for customers, for users, for the community, for your teammates, right?

609
00:54:15,320 --> 00:54:16,520
In a positive way.

610
00:54:16,570 --> 00:54:19,760
And I feel like what you're doing for PGConf.dev is definitely high impact.

611
00:54:20,920 --> 00:54:25,020
Anybody else who agrees with me on that should be sure to tell Melanie's boss.

612
00:54:27,460 --> 00:54:31,420
But has that an event for Postgres virtual February 1st is the deadline.

613
00:54:32,340 --> 00:54:37,960
And I really appreciate your help sifting through all of those proposals and finding,

614
00:54:38,160 --> 00:54:43,380
OK, what are the right set of 40 virtual talks that we should record and publish?

615
00:54:44,140 --> 00:54:50,360
[MELANIE] POSETTE has a higher volume of submissions to review usually, but for dev I also rewatch

616
00:54:50,640 --> 00:54:56,920
every single talk from the previous year, or I did last year and this year, and watch

617
00:54:56,990 --> 00:55:00,400
talks from every single submitter if I haven't seen them speak before.

618
00:55:01,300 --> 00:55:03,360
So it takes a really long time to review those.

619
00:55:04,940 --> 00:55:11,420
[CLAIRE] Well one of the things that I learned about you in one of the previous podcast episodes where you

620
00:55:11,500 --> 00:55:18,780
joined Talking Postgres is you told me about, you're a runner, and you told me about how you will often

621
00:55:19,120 --> 00:55:24,400
listen to conference talks that are published on YouTube or whatever. Hopefully you're not

622
00:55:24,720 --> 00:55:28,960
looking at the YouTube video while you're running, but you'll be out there on the streets of

623
00:55:29,420 --> 00:55:35,120
Pennsylvania listening to these conference talks as a way to like get your exercise done and learn

624
00:55:35,280 --> 00:55:35,720
something new.

625
00:55:35,920 --> 00:55:39,180
[MELANIE] That is how I manage to watch them all, just to be clear.

626
00:55:39,200 --> 00:55:44,400
I don't sit and watch all of them in a row while doing, you know, I do it while running,

627
00:55:45,320 --> 00:55:49,720
which means that I've gotten very good at trying to understand what people say without any visuals.

628
00:55:50,620 --> 00:55:56,840
[CLAIRE] Yeah and without the captions, right? I always turn captions on when I'm watching um I'm watching

629
00:55:57,020 --> 00:56:01,660
anything whether I'm watching a technical video on YouTube or watching Netflix on my TV.

630
00:56:02,840 --> 00:56:05,120
So yeah, you don't get captions when you do that.

631
00:56:05,680 --> 00:56:13,520
But what's cool about the fact that PGConf.dev records the talks is that, and not all

632
00:56:13,660 --> 00:56:19,720
conferences do that, but I think it makes the business justification even stronger for

633
00:56:19,380 --> 00:56:19,720
a speaker.

634
00:56:20,340 --> 00:56:24,680
Because it's not just that they're going to reach the people in the room, but they have

635
00:56:24,680 --> 00:56:27,600
the potential to reach many, many more people online digitally.

636
00:56:28,300 --> 00:56:33,220
[MELANIE] Yeah, and so in Robert's hacking workshops, about 80% of the talks, I would say, come from

637
00:56:33,420 --> 00:56:33,620
dev.

638
00:56:35,400 --> 00:56:37,400
[CLAIRE] When you say dev, you mean PGConf.dev?

639
00:56:37,380 --> 00:56:38,740
[MELANIE] Yeah, from PGConf.dev. [Okay.]

640
00:56:39,560 --> 00:56:44,840
Just because it has a lot of, like, hacking-related talks compared to other conferences.

641
00:56:46,180 --> 00:56:47,400
And they record.

642
00:56:48,220 --> 00:56:55,000
So that's one way that the content is getting used in the community for other sort

643
00:56:55,040 --> 00:56:58,800
of like educational and collaboration focus events.

644
00:56:58,010 --> 00:56:58,140
[CLAIRE] Okay,

645
00:56:59,300 --> 00:57:06,240
so context for people who are listening, Robert is Robert Haas, he's a Postgres major contributor

646
00:57:06,660 --> 00:57:15,180
and committer, long time person involved with the project and about a year and a half ago

647
00:57:15,920 --> 00:57:22,340
he started this new Postgres mentoring program and created a Postgres hacking Discord to kind of

648
00:57:22,620 --> 00:57:25,180
be the platform for it.

649
00:57:25,460 --> 00:57:30,640
And it actually came out of an unconference session at PGConf.dev

650
00:57:29,460 --> 00:57:33,580
that was in Vancouver that that year, 2024.

651
00:57:35,120 --> 00:57:39,340
And so they have these in addition to like having cohorts of mentors

652
00:57:39,400 --> 00:57:44,060
and mentees who he matches together, they have these monthly hacking workshops

653
00:57:44,520 --> 00:57:48,700
where everybody agrees to watch a talk that's been published online.

654
00:57:49,220 --> 00:57:54,400
And then you get together and talk about it and answer questions, drill down, debate, whatever.

655
00:57:55,640 --> 00:57:59,620
And you have to you sign up for these hacking workshops and you have to attend.

656
00:58:00,080 --> 00:58:02,280
He keeps track of who signs up and doesn't show up.

657
00:58:02,390 --> 00:58:04,240
So I think there's very few no shows.

658
00:58:04,750 --> 00:58:10,240
And he does it in a couple of different time zones so that somebody from APAC and somebody from America, you know what I mean?

659
00:58:10,240 --> 00:58:13,740
It can work out regardless of what part of the world you live in.

660
00:58:15,180 --> 00:58:20,940
And I don't know, Melanie, maybe you can share your perspective on this whole mentorship program and the hacker workshop.

661
00:58:21,240 --> 00:58:29,780
But I think it's a really cool testament to PGConf.dev that this thing even exists in part because of the unconference at PGConf.dev.

662
00:58:31,040 --> 00:58:36,800
[MELANIE] Yeah, I'm always very excited when we have initiatives that people do that some of the

663
00:58:36,860 --> 00:58:39,720
conversation started there, projects or features.

664
00:58:40,920 --> 00:58:41,520
[CLAIRE] That's really cool.

665
00:58:42,000 --> 00:58:48,580
And I have had Robert Haas on the this podcast, Talking Postgres, which is how I knew everything that I shared.

666
00:58:49,040 --> 00:58:51,680
I've only attended, I think, one of the hacking workshops.

667
00:58:53,460 --> 00:58:59,000
So I don't have a ton of context on like exactly what they're like because I only went to one.

668
00:59:00,520 --> 00:59:10,520
But I will share a link to the Robert Haas episode because for anybody who's ever thought about the challenges of mentorship and how to create structure around it,

669
00:59:10,580 --> 00:59:12,840
it should be useful to listen to that one.

670
00:59:14,120 --> 00:59:21,520
[MELANIE] And coming back to the CFP, so what I've told people, and I will keep doing this, if you

671
00:59:22,060 --> 00:59:28,920
want me to review your submission and give you feedback, if you submit now, like, you

672
00:59:28,940 --> 00:59:33,820
know, within the next couple of weeks, so before the deadline, and ask me to do it specifically,

673
00:59:33,880 --> 00:59:35,920
like I will probably do it.

674
00:59:35,940 --> 00:59:37,200
I haven't gotten very many requests,

675
00:59:37,440 --> 00:59:38,760
so I've been able to manage it.

676
00:59:39,280 --> 00:59:41,780
But like, I'm happy to give you feedback

677
00:59:41,820 --> 00:59:43,380
if you want to know how could I make this

678
00:59:43,480 --> 00:59:45,420
more relevant to the audience or whatever.

679
00:59:47,240 --> 00:59:49,920
But like, you know, if it's the day before,

680
00:59:50,040 --> 00:59:50,960
I probably won't do it.

681
00:59:51,940 --> 00:59:55,020
[CLAIRE] Well because you're going to have too many people asking you in the the days

682
00:59:55,580 --> 01:00:00,480
right before because so many people are deadline driven that is a really generous offer um

683
01:00:01,600 --> 01:00:03,860
and I think that if for some reason you find it too intimidating to reach out to Melanie

684
01:00:09,700 --> 01:00:12,920
for feedback on your CFP submission,

685
01:00:13,080 --> 01:00:14,740
first of all, she's awesome.

686
01:00:15,200 --> 01:00:18,980
And I guess I would say don't feel intimidated,

687
01:00:19,300 --> 01:00:23,420
but people can't help their feelings.

688
01:00:21,240 --> 01:00:23,000
But the other thing I would say is

689
01:00:23,800 --> 01:00:26,080
just do get somebody you trust

690
01:00:26,140 --> 01:00:28,960
to review your talk submissions before they go in.

691
01:00:33,880 --> 01:00:49,880
[MELANIE] You can't feel intimidated by me if you've seen me do Spice Girls karaoke. So yes thank you thanks to Boriss for encouraging me to do more karaoke in public.

692
01:00:37,640 --> 01:00:39,480
[CLAIRE] Which I understand you did.

693
01:00:39,520 --> 01:00:43,540
at PGConf.EU a couple months ago in Latvia, right?

694
01:00:54,740 --> 01:00:59,740
So there's another question from Boriss on the chat asking, you had mentioned earlier that when

695
01:00:59,940 --> 01:01:04,540
you are coding, you like to get in the zone, if you will, and you don't check messages or

696
01:01:04,560 --> 01:01:13,580
notifications at all, which is great. What else do you do to get into the zone? Music, headset, tea, coffee, water?

697
01:01:14,300 --> 01:01:19,300
[MELANIE] I have a white noise, I have a white noise machine that I will use if I think that I'm

698
01:01:19,380 --> 01:01:26,980
going to be interrupted but um basically I just I prefer as much quiet as possible and if I'm

699
01:01:27,120 --> 01:01:32,280
thinking and not actually coding I like to curl up into a ball on the ground so I'd like the

700
01:01:32,540 --> 01:01:38,060
opposite of people that say they do their best thinking while walking or whatever I'm like

701
01:01:38,800 --> 01:01:39,820
stillness and silence

702
01:01:42,200 --> 01:01:45,540
[CLAIRE] That's amazing. I've never heard that before from anybody.

703
01:01:46,020 --> 01:01:50,080
[MELANIE] It's a weird thing that I've now shared publicly in a podcast, so.

704
01:01:50,740 --> 01:01:58,000
[CLAIRE] Yeah, so I'm so the opposite of that I do my best thinking in the shower, you know walking,

705
01:01:58,960 --> 01:02:04,940
typing, like writing, scribbling, doodling. I have to, my hands, I guess, need to be busy

706
01:02:05,580 --> 01:02:09,260
or my legs. Right. But you curl up in a ball.

707
01:02:09,360 --> 01:02:10,120
[MELANIE] Yeah,

708
01:02:10,140 --> 01:02:12,160
I guess it's like the fetal position. Maybe it...

709
01:02:12,720 --> 01:02:15,240
[CLAIRE] Okay. Wait, don't you have cats? Do you have cats?

710
01:02:15,580 --> 01:02:16,740
[MELANIE] I do have a cat. Yeah.

711
01:02:17,120 --> 01:02:20,260
[CLAIRE] Is the cat curled up with you? Are you actually petting the cat?

712
01:02:21,020 --> 01:02:25,880
[MELANIE] No, she's not allowed in the room when I have to think carefully because she's very distracting.

713
01:02:26,800 --> 01:02:33,880
[CLAIRE] Oh, that's, that's good to know. Okay. So no pets is part of the equation for deep thinking too. Okay.

714
01:02:40,040 --> 01:02:43,060
[MELANIE] So yeah, yeah. It kind of works out that I work from home because I definitely couldn't do the curling up in a ball on the floor thing in an office.

715
01:02:43,810 --> 01:02:46,180
[CLAIRE] I think people might start to get worried about you.

716
01:02:46,660 --> 01:02:47,520
[MELANIE] Yeah, I agree.

717
01:02:49,660 --> 01:02:52,220
[CLAIRE] So there's something else that I'm curious about.

718
01:02:52,460 --> 01:02:58,740
If somebody is listening to this podcast episode and they get really inspired about what you're

719
01:02:58,880 --> 01:03:03,240
trying to do with PGConf.dev, serving the different needs of different people in the

720
01:03:03,420 --> 01:03:04,220
audience, right?

721
01:03:04,760 --> 01:03:11,500
Whether existing or future community members and contributors or users, and they want to

722
01:03:11,760 --> 01:03:11,920
help.

723
01:03:12,640 --> 01:03:16,300
Is that, I mean, I'm pitching you a softball here, but take it.

724
01:03:13,820 --> 01:03:13,900
[MELANIE] Yes.

725
01:03:17,540 --> 01:03:18,860
We really love volunteers.

726
01:03:20,500 --> 01:03:23,960
So there's a lot to do when it gets closer to the event.

727
01:03:24,260 --> 01:03:25,680
There's some things to do now.

728
01:03:27,200 --> 01:03:31,960
But we definitely, like, we had a few people sign up to volunteer,

729
01:03:32,210 --> 01:03:36,380
and we've found tasks for them, and then we have more tasks.

730
01:03:36,380 --> 01:03:39,980
So there's things like helping us find a speaker gift that is, like,

731
01:03:39,980 --> 01:03:42,900
a local Vancouver thing, right?

732
01:03:44,300 --> 01:03:48,540
There's a list of things like that.

733
01:03:50,220 --> 01:03:54,160
And we always need help with, like, design things.

734
01:03:55,260 --> 01:03:57,000
It's pretty hard to get design volunteers.

735
01:03:57,420 --> 01:04:00,020
But, like, there are lots of things that go into the conference,

736
01:04:00,170 --> 01:04:01,360
and we need help with all of them.

737
01:04:01,360 --> 01:04:07,460
And if you aren't free in advance, then on-site we need tons of volunteers

738
01:04:07,790 --> 01:04:09,640
for being room hosts.

739
01:04:09,790 --> 01:04:12,500
And then things, like, set up and tear down.

740
01:04:12,700 --> 01:04:17,960
just like any other conference, but we also have sort of unique opportunities. Like we have

741
01:04:18,380 --> 01:04:22,940
the novice breakfast, or we're probably not going to call it that, but the new to Postgres breakfast,

742
01:04:23,220 --> 01:04:29,280
like we'll need experienced community people to meet and greet and network and interact. And that

743
01:04:29,340 --> 01:04:34,180
one's, I think we're going to probably get a good number of students at that. Right. So if you like

744
01:04:34,320 --> 01:04:38,440
talking to students about Postgres or whatever, we need people to do that. We need people to,

745
01:04:39,580 --> 01:04:47,600
you know, volunteer to help with like organizing the panels and we like to, you know, to onsite.

746
01:04:47,870 --> 01:04:53,820
We need people to help with the slideshow. We need people to volunteer to, with the meet and

747
01:04:53,870 --> 01:04:59,620
eat groups, like finding restaurants for them to, to actually be at. And a lot of this helps if you

748
01:04:59,720 --> 01:05:03,140
kind of know Vancouver, but you could do it remotely, you could look at Yelp or whatever.

749
01:05:04,800 --> 01:05:07,880
So there's tons of tons of stuff.

750
01:05:07,910 --> 01:05:14,460
We need someone to we have the T-shirt design almost finalized, but we need to order it and do the size breakdown, like all of that kind of stuff.

751
01:05:14,490 --> 01:05:15,740
So there's normal conference stuff.

752
01:05:16,160 --> 01:05:20,040
And then there's stuff that's kind of specific, like to the interactive content.

753
01:05:20,850 --> 01:05:23,160
Like we need people to lead meet and eat groups.

754
01:05:23,420 --> 01:05:25,580
Right. So there's a lot of opportunities.

755
01:05:25,800 --> 01:05:33,180
So you can totally reach out to me or there's a PGConf.dev Discord, which I feel like we should have linked here.

756
01:05:33,480 --> 01:05:34,680
I totally forgot about that.

757
01:05:35,580 --> 01:05:39,760
[CLAIRE] We'll add that to the show notes that's a great idea so if people are planning on attending

758
01:05:40,400 --> 01:05:46,180
um you there's no reason to wait until the week before the conference if the Discord is open and

759
01:05:46,200 --> 01:05:49,340
available now, people could join now, right? But even though there's not going to be a lot

760
01:05:50,620 --> 01:05:54,680
of conversation until we get closer, I imagine. Is that right?

761
01:05:54,760 --> 01:05:54,940
[MELANIE] Great.

762
01:05:55,020 --> 01:05:56,200
We won't be spamming you.

763
01:05:56,420 --> 01:05:59,420
Like, you won't have to worry if you join that there'll be notifications all the time.

764
01:05:59,540 --> 01:06:24,680
But we do put big announcements like, okay, the CFP is open, and you can follow us on social for that too. So there'll be stuff like that. And then once it gets closer, things like coordinating your meet and eat group or whatever special things you're going to in the actual event, there'll be basically like birds of a feather groups and things like that,

765
01:06:25,840 --> 01:06:32,240
all the collaboration will be there and you can contact all the organizers are on there as well.

766
01:06:32,380 --> 01:06:32,520
[CLAIRE] Okay.

767
01:06:33,190 --> 01:06:35,740
So you just said you can follow us on social.

768
01:06:35,930 --> 01:06:43,140
So we'll add links to your, the PGConf.dev LinkedIn account, Bluesky account, Mastodon

769
01:06:43,320 --> 01:06:43,500
account.

770
01:06:43,500 --> 01:06:45,320
Are those the three primary ones?

771
01:06:45,590 --> 01:06:46,180
Am I right?

772
01:06:46,819 --> 01:06:51,060
[MELANIE] We still have, I think we still have X as well, but the primary one, I'd say LinkedIn is our most

773
01:06:53,200 --> 01:06:54,120
popular platform.

774
01:06:55,000 --> 01:06:56,040
[CLAIRE] Yeah so definitely follow there or whichever platform you're on um that's a good

775
01:07:02,860 --> 01:07:07,940
way to stay in touch, um you just pitched me a softball you didn't realize it you didn't do it

776
01:07:07,800 --> 01:07:13,540
on purpose but I want to take advantage you mentioned design. So um for anybody who likes

777
01:07:13,560 --> 01:07:18,860
the PGConf.dev logo i just want to point out that the designer for that is someone named Isaac

778
01:07:18,880 --> 01:07:27,920
Alves. So I work at Microsoft and Isaac's company, MUXWilliams, we hire them to do various and

779
01:07:28,100 --> 01:07:35,340
sundry things. And so we asked Isaac to create that logo. He actually created like five or six

780
01:07:35,500 --> 01:07:40,380
different ones that we offered to PGConf.dev. And the one you're using is the one you picked,

781
01:07:40,620 --> 01:07:46,420
obviously. And I just think it's absolutely gorgeous. And it's everywhere on all of your,

782
01:07:46,640 --> 01:07:49,300
you know social platforms website t-shirts everything.

783
01:07:49,820 --> 01:07:53,420
[MELANIE] We just love what he came up with and he's helping us with some of the anniversary

784
01:07:53,660 --> 01:07:57,620
content like design too.

785
01:07:58,340 --> 01:08:04,920
[CLAIRE] Yeah, so shout out shout out to Isaac Alves, and in fact in that Nairobi um meetup that you mentioned

786
01:08:05,600 --> 01:08:10,620
that just happened I guess a couple days ago or last week or something um the one of the LinkedIn

787
01:08:10,660 --> 01:08:17,020
post, which I will include in the show notes, has a picture of, was it Monica, wearing a PGConf.dev

788
01:08:17,170 --> 01:08:20,799
t-shirt, like front and center on that post, which I thought was kind of cool.

789
01:08:21,020 --> 01:08:21,940
[MELANIE] Yeah, that was awesome.

790
01:08:22,160 --> 01:08:29,540
She talked about her experience going so uh at the and like one of

791
01:08:29,540 --> 01:08:34,779
the things people said who went was like oh you made this conference sound so cool so I was happy

792
01:08:34,940 --> 01:08:35,180
about that.

793
01:08:35,839 --> 01:08:40,620
[CLAIRE] So if you're still listening to this episode, you made it all the way through and you're

794
01:08:40,640 --> 01:08:45,520
here then you probably care about Postgres and maybe you're even interested in PGConf.dev

795
01:08:46,319 --> 01:08:53,520
what I would encourage you to do is think about whether you have some content or ideas to submit

796
01:08:53,720 --> 01:08:58,799
to the CFP, but even if you don't put the dates on your calendar and start trying to make

797
01:08:58,900 --> 01:09:04,940
sure you have budget to be able to fly and attend when it happens in May. The CFP close date is,

798
01:09:04,960 --> 01:09:05,640
tell me again, Melanie.

799
01:09:06,259 --> 01:09:07,580
[MELANIE] January 16th.

800
01:09:07,660 --> 01:09:13,660
[CLAIRE] OK, and and if you don't listen to this episode for six months and you miss the chance to

801
01:09:14,100 --> 01:09:16,020
submit, it'll happen again next year.

802
01:09:16,660 --> 01:09:18,180
And so, you know, plan for it.

803
01:09:18,259 --> 01:09:19,200
It's always in May.

804
01:09:19,339 --> 01:09:19,839
Is that right?

805
01:09:20,480 --> 01:09:21,740
[MELANIE] Yeah, it is always in May.

806
01:09:21,960 --> 01:09:27,259
[CLAIRE] OK, and will you announce the dates for 2027 when we're all there in 2026?

807
01:09:28,040 --> 01:09:31,100
[MELANIE] Yeah we'll probably announce it sooner because we've almost finished.

808
01:09:31,529 --> 01:09:36,720
We've already decided where it's going to be and we are almost done.

809
01:09:36,779 --> 01:09:40,700
[CLAIRE] Is it still secret can you tell us now, can you announce it now on this podcast?

810
01:09:41,400 --> 01:09:44,060
[MELANIE] Probably not until we book the venue because maybe someone will like

811
01:09:44,380 --> 01:09:45,859
snipe the venue from us or something.

812
01:09:46,839 --> 01:09:54,540
[CLAIRE] Okay, so then the last thing I would also say is um the I'll just remind you all too that the

813
01:09:54,620 --> 01:09:56,600
POSETTE CFP is going to close on February 1st.

814
01:09:56,870 --> 01:10:07,160
So if you're listening to this and you're thinking a virtual event might be the way for you to share your expertise, your story, your successes, your failures, do check out the POSETTE CFP, too.

815
01:10:07,800 --> 01:10:08,080
Melanie...

816
01:10:08,700 --> 01:10:11,460
[MELANIE] Thanks for the opportunity to talk about this Claire because

817
01:10:11,520 --> 01:10:13,440
not very many conferences

818
01:10:13,740 --> 01:10:15,140
get to have a podcast episode

819
01:10:15,620 --> 01:10:18,720
about how you should submit to their CFP.

820
01:10:19,720 --> 01:10:24,960
[CLAIRE] I knew that you would have a lot to say about about this conference.

821
01:10:25,960 --> 01:10:26,600
And it's important.

822
01:10:26,730 --> 01:10:27,900
I think it's important to the project.

823
01:10:28,220 --> 01:10:33,620
So I am super happy to dedicate this podcast episode to PGConf.dev and to you.

824
01:10:34,080 --> 01:10:37,140
And shout out also to the other organizers for the conference.

825
01:10:37,480 --> 01:10:45,940
So just before we say goodbye, can you remind me who is serving on the organizing team this year?

826
01:10:46,600 --> 01:10:47,980
[MELANIE] Sure, yeah.

827
01:10:48,260 --> 01:10:53,380
So it's the same organizers as last year, except for Gwen is new.

828
01:10:53,580 --> 01:10:59,420
So Jonathan Katz and me and Paul Ramsey and Steve Singer and Robert Haas.

829
01:10:59,860 --> 01:11:01,760
And then Gwen Shapira joined us this year.

830
01:11:01,920 --> 01:11:03,940
And also my husband, Kaiting Chen.

831
01:11:04,500 --> 01:11:09,400
He was, he's a Postgres user, but hadn't been involved in the community really.

832
01:11:09,980 --> 01:11:12,480
And then he saw how much work it was for me.

833
01:11:12,480 --> 01:11:14,840
And he was like, okay, I'm going to join.

834
01:11:14,960 --> 01:11:17,360
And he takes an engineering approach to everything.

835
01:11:17,560 --> 01:11:18,940
And he's like, you guys can be more efficient.

836
01:11:19,140 --> 01:11:20,060
I'm going to make you more efficient.

837
01:11:20,240 --> 01:11:24,280
And then it'll be, it'll take up less of your time and you can hang out with me more.

838
01:11:24,620 --> 01:11:25,640
So that was his agenda.

839
01:11:26,200 --> 01:11:32,820
But now it's cute because he has like, you know, he goes to events and he has his Postgres people that he knows and hangs out with.

840
01:11:32,820 --> 01:11:34,740
And they're different people than I hang out with.

841
01:11:34,780 --> 01:11:38,020
And so it's been really cool to see, see that.

842
01:11:39,300 --> 01:11:44,860
[CLAIRE] What's also cool when we think about it from a like Postgres ecosystem perspective, oh and by the way

843
01:11:44,940 --> 01:11:45,980
I'm a big Kaiting fan.

844
01:11:46,180 --> 01:11:50,180
So but I'm pivoting from the Kaiting focus of the conversation to say that,

845
01:11:50,800 --> 01:11:53,460
like, I think all of you work at different companies.

846
01:11:53,600 --> 01:11:54,460
So you're from Microsoft. [Yes.]

847
01:11:55,860 --> 01:11:58,480
Jonathan Katz is at Databricks now. [Yes.]

848
01:11:58,560 --> 01:11:59,300
Gwen's at Nile.

849
01:11:59,720 --> 01:12:02,520
Paul is at Crunchy Data, which was acquired by Snowflake.

850
01:12:02,640 --> 01:12:03,620
So I should say Snowflake.

851
01:12:04,020 --> 01:12:08,640
Robert Haas works at EDB and Steve Singer works at Nav Technologies and Kaiting.

852
01:12:09,300 --> 01:12:10,660
It says Domino Data Lab.

853
01:12:10,780 --> 01:12:11,260
Is that right?

854
01:12:11,740 --> 01:12:13,840
[MELANIE] Yeah, he started there a couple months ago.

855
01:12:13,980 --> 01:12:14,480
So, yeah.

856
01:12:14,520 --> 01:12:20,840
[CLAIRE] Okay, awesome. So I like that kind of diversity of background. And of course, shout out to all

857
01:12:20,960 --> 01:12:27,500
those companies who like support their people working on this, right? In addition to every

858
01:12:27,890 --> 01:12:28,760
everything else that you do.

859
01:12:29,060 --> 01:12:34,880
[MELANIE] Oh, I forgot Magnus Hagander is also an organizer, but he's not on the website because

860
01:12:34,890 --> 01:12:39,740
he didn't give us his picture yet. Sorry. So Magnus is also there. He is critical to

861
01:12:42,700 --> 01:12:45,700
all of our tech infrastructure for the conference.

862
01:12:46,240 --> 01:12:47,380
So very important.

863
01:12:48,940 --> 01:12:50,400
But yeah, no, it's a ton of work.

864
01:12:50,580 --> 01:12:53,400
And I'm really grateful to all of our employers

865
01:12:53,820 --> 01:12:57,780
for supporting the community by letting us do this, you know?

866
01:12:59,560 --> 01:13:04,460
[CLAIRE] And then the program committee um is listed on the CFP page as well so um and that's you Melanie [Yes.]

867
01:13:06,360 --> 01:13:10,300
and Dilip Kumar, Jonathan Katz, Paul Ramsey and Jacob Champion, who is the newest Postgres

868
01:13:13,180 --> 01:13:16,160
committer as of earlier in 2025, right?

869
01:13:16,800 --> 01:13:20,060
[MELANIE] Yes, I have a secret agenda to eventually not be on the program committee.

870
01:13:20,300 --> 01:13:21,540
So as I like switch out people each year and like, I'm looking for the next program committee chair.

871
01:13:30,140 --> 01:13:39,100
So if you're interested in doing it too, like, you know, one thing that we're trying to do is give, I think for the lightning talks,

872
01:13:40,560 --> 01:13:44,980
talk selection, we're going to try to bring someone new in. We're trying to get more community

873
01:13:45,160 --> 01:13:49,680
people involved in these kinds of things and give them more opportunities to be on committees.

874
01:13:49,800 --> 01:13:51,000
And yeah.

875
01:13:52,160 --> 01:14:01,200
[CLAIRE] Yeah, it and I think it helps sometimes to attend a conference and also have a job to do beyond just learning and networking.

876
01:14:02,780 --> 01:14:13,220
So if you have something that you're volunteering for or a panel that you're hosting or a committee that you're serving on some way that you're helping, I don't know.

877
01:14:13,420 --> 01:14:17,900
It's an additional sense of purpose as to the business justification, if you will.

878
01:14:18,640 --> 01:14:21,400
OK, Melanie, I love working with you.

879
01:14:21,480 --> 01:14:26,860
I really do. And I am so thankful that you joined us today to talk about something that you have

880
01:14:27,080 --> 01:14:35,540
some opinions on.

881
01:14:28,840 --> 01:14:30,200
[MELANIE] Yeah, thanks for having me.

882
01:14:36,300 --> 01:14:42,600
[CLAIRE] Melanie has opinions on lots of things. Don't worry, people. Okay. With that, we are going to wrap. So thank you so much to Melanie Plageman for joining us. If you liked

883
01:14:42,860 --> 01:14:48,440
today's episode and you want to hear more of these Talking Postgres episodes, you should subscribe

884
01:14:48,440 --> 01:14:54,580
on Spotify, Apple, YouTube, or wherever you get your podcasts. And please tell your friends.

885
01:14:55,060 --> 01:15:00,900
If you leave a review, that helps even more people discover the podcast. So you can get

886
01:15:01,060 --> 01:15:07,140
to past episodes as well and get links to subscribe at TalkingPostgres.com. And transcripts

887
01:15:07,140 --> 01:15:12,680
are included on the episode pages on TalkingPostgres.com too. A big thank you to everybody

888
01:15:12,820 --> 01:16:28,400
who joined the live recording and participated in the live text chat on Discord.