1
00:00:05,300 --> 00:00:10,080
[CLAIRE] Welcome to Talking Postgres, a monthly
podcast for developers who love Postgres.

2
00:00:10,600 --> 00:00:12,180
I'm your host, Claire Giordano,

3
00:00:12,640 --> 00:00:17,900
and in this podcast, we will explore the human
side of Postgres databases and open source,

4
00:00:18,360 --> 00:00:22,000
which means why do people who work with
Postgres do what they do and how did

5
00:00:22,020 --> 00:00:22,480
they get there?

6
00:00:23,140 --> 00:00:27,780
I want to say thank you to the team at Microsoft
for sponsoring today's community conversation.

7
00:00:28,600 --> 00:00:31,660
Today's guest, without further
ado, is Peter Eisentraut.

8
00:00:32,220 --> 00:00:36,540
Peter is an open source committer
to the Postgres project.

9
00:00:37,000 --> 00:00:38,760
He serves on the Postgres core team.

10
00:00:39,140 --> 00:00:45,060
He serves on the board for the PGCA nonprofit
that protects the trademark. He serves

11
00:00:45,100 --> 00:00:50,280
on the database standards working
group that evolves the SQL standard. He

12
00:00:50,800 --> 00:00:55,740
is employed at EDB, where he is a VP
and chief architect of database servers,

13
00:00:56,260 --> 00:00:59,280
and he's the former CTO of 2ndQuadrant.

14
00:00:59,620 --> 00:01:03,980
One of the things I particularly like about
Peter's work experience is that he worked at

15
00:01:04,040 --> 00:01:10,440
Sun Microsystems early in his career, and he's
just a brilliant engineer and engineering leader.

16
00:01:10,800 --> 00:01:14,800
So I am really happy that you decided
to come on the podcast. Welcome.

17
00:01:14,860 --> 00:01:19,060
[PETER] Thank you. Thank you for
having me. Very excited to talk to you.

18
00:01:20,460 --> 00:01:26,880
[CLAIRE] The title of today's episode is
probably why I had such a long introduction.

19
00:01:27,640 --> 00:01:31,100
So many things, so many different types
of contributions that you're making.

20
00:01:31,940 --> 00:01:35,200
And the title is 25 Years
of Contributing to Postgres.

21
00:01:35,920 --> 00:01:39,200
And I'm hoping that by the end
of the episode, we will know

22
00:01:39,740 --> 00:01:44,600
a bit more about why you've
stayed for 25 years, right?

23
00:01:44,700 --> 00:01:48,340
Why you kept coming back for
more every step of the way.

24
00:01:48,480 --> 00:01:52,020
And if you don't know the answer to that
yet, hopefully you will figure it out

25
00:01:52,080 --> 00:01:52,720
along with me.

26
00:01:53,480 --> 00:01:54,260
[PETER] That would be good, yes.

27
00:01:54,780 --> 00:01:58,560
[CLAIRE] In today's conversation,
let's start with your origin story.

28
00:01:59,180 --> 00:02:01,880
We do a lot of origin stories on this podcast.

29
00:02:02,240 --> 00:02:04,480
I'm really curious just how you got started.

30
00:02:05,240 --> 00:02:07,700
As a developer, forget about
Postgres for a second, just

31
00:02:08,199 --> 00:02:10,759
how did you get started at the keyboard and in

32
00:02:11,600 --> 00:02:11,980
software?

33
00:02:14,600 --> 00:02:16,440
[PETER] I think I got started very early

34
00:02:17,300 --> 00:02:21,600
in my childhood even just tinkering
with computers or programming, really.

35
00:02:21,680 --> 00:02:26,280
Not so much hardware tinkering perhaps, but
just with a computer. A computer was there and

36
00:02:26,860 --> 00:02:30,260
maybe in other circumstances you would
play games or something. But I was,

37
00:02:30,900 --> 00:02:32,580
the first thing I did was write a little program.

38
00:02:33,720 --> 00:02:37,160
The first computer I worked on was a Commodore 64,

39
00:02:37,980 --> 00:02:41,780
so it was basic programming, and you
just sort of wrote some loops and had it

40
00:02:41,820 --> 00:02:43,480
print something, that kind of stuff.

41
00:02:43,580 --> 00:02:46,640
So it was really very early on that
I liked programming, essentially.

42
00:02:47,420 --> 00:02:48,760
[CLAIRE] Do you remember how old you were?

43
00:02:51,520 --> 00:02:57,340
[PETER] I was probably somewhere
12, 13, something like that perhaps.

44
00:02:56,940 --> 00:02:57,240
[CLAIRE] OK.

45
00:02:57,900 --> 00:03:02,980
But where did you get the idea to write
a program instead of playing a game

46
00:03:03,040 --> 00:03:08,320
or something like that? Is it something
that you saw someone else do or?

47
00:03:10,300 --> 00:03:12,260
Do you remember where the inspiration came from?

48
00:03:13,520 --> 00:03:15,180
[PETER] I don't know. I think my...

49
00:03:17,060 --> 00:03:20,400
you know, back in those days, we didn't
have a lot of computers around, so it's

50
00:03:20,460 --> 00:03:24,240
hard to know where you get inspirations
for that, like that kind of thing.

51
00:03:24,280 --> 00:03:29,260
And it wasn't maybe something I
saw at work at my dad's place.

52
00:03:30,740 --> 00:03:35,240
You know, there was computers there, and
I saw people programming, perhaps, right?

53
00:03:35,300 --> 00:03:36,560
That's the only...

54
00:03:37,940 --> 00:03:42,300
that kind of thing I could have seen
before, but other than that, I don't know.

55
00:03:42,400 --> 00:03:44,700
I think you just sort of like,
oh, this is the kind of thing I,

56
00:03:45,480 --> 00:03:49,060
maybe it's just something that I found,
oh, I could do this. This is interesting

57
00:03:50,060 --> 00:03:51,180
without even knowing why.

58
00:03:52,740 --> 00:03:56,760
[CLAIRE] Well, I'm glad you did, because I'm glad
something got you started on your path toward

59
00:03:56,840 --> 00:04:02,920
Postgres. What happened next?
And then how did you get from

60
00:04:03,720 --> 00:04:08,200
working with computers or being a
developer into working with Postgres.

61
00:04:09,760 --> 00:04:09,880
[PETER] Well,

62
00:04:11,660 --> 00:04:14,820
I think for a long time, really not
much happened after that, right?

63
00:04:14,900 --> 00:04:18,781
I wasn't working with computers at
home during my school years much.

64
00:04:19,860 --> 00:04:23,959
Though we didn't have a computer, or I didn't
have one personally. You know, back then,

65
00:04:24,540 --> 00:04:30,900
you didn't necessarily have one for yourself. But
it certainly was always interesting to me, and

66
00:04:32,320 --> 00:04:35,620
I think it was not until college that I then,

67
00:04:36,520 --> 00:04:39,780
you know, decided that I was going
to study computer science and

68
00:04:41,539 --> 00:04:45,920
I had to get a computer and then
started programming either at school or,

69
00:04:46,960 --> 00:04:51,120
yeah, I think at school mostly in the
computer labs and then also at home, and

70
00:04:51,240 --> 00:04:52,720
I had my own machine.

71
00:04:53,900 --> 00:04:55,440
But it was the same thing, right? You...

72
00:04:56,555 --> 00:05:01,660
I wasn't really much into playing games. The
internet was just getting started at the time,

73
00:05:02,420 --> 00:05:06,360
so you could get a lot of information
online and that kind of thing.

74
00:05:06,400 --> 00:05:07,500
Maybe that was like a good

75
00:05:08,080 --> 00:05:10,560
sort of, I came in just at the right time where

76
00:05:11,100 --> 00:05:12,420
some of those things were taking off.

77
00:05:15,240 --> 00:05:15,620
[CLAIRE] And then.

78
00:05:15,260 --> 00:05:18,100
[PETER] But yeah, it was just fun
tinkering around and learning, you know,

79
00:05:18,840 --> 00:05:23,420
programming languages and figuring just,
yeah, I think it was always like that.

80
00:05:24,360 --> 00:05:28,600
[CLAIRE] Maybe we should rename the episode to
25 years of tinkering with Postgres, just to get

81
00:05:28,620 --> 00:05:31,120
the word tinker in there. I like
how it rolls off the tongue.

82
00:05:31,800 --> 00:05:33,860
[PETER] Yeah, I think it
is like that though, right?

83
00:05:34,000 --> 00:05:37,720
Not all of it necessarily has to
lead to something, right? It's just

84
00:05:38,700 --> 00:05:41,700
seeing what the thing can do and
what the new technology can do,

85
00:05:44,320 --> 00:05:44,820
out of interest.

86
00:05:46,140 --> 00:05:48,640
[CLAIRE] Okay, so first encounter
with Postgres. When was that?

87
00:05:50,680 --> 00:05:54,000
[PETER] I was, that was in college. I was

88
00:05:55,500 --> 00:05:58,620
doing an internship, so this
was part of the computer science

89
00:05:59,320 --> 00:06:01,880
program. I was doing an internship at a

90
00:06:03,060 --> 00:06:08,160
internet service provider at the time
provided dial-up to sort of the city,

91
00:06:09,828 --> 00:06:10,428
and

92
00:06:11,768 --> 00:06:15,248
they basically just heard, oh, you
know programming, you know SQL.

93
00:06:16,708 --> 00:06:20,688
You know, come work with
us. You can be our database

94
00:06:22,088 --> 00:06:26,048
DBA or I guess something like that. We
need someone who knows that kind of thing.

95
00:06:26,568 --> 00:06:29,348
And they were using Postgres, which
I think was unheard of at the time.

96
00:06:30,368 --> 00:06:35,728
But somehow they just decided to use
it and wanted me to help develop their

97
00:06:37,728 --> 00:06:41,468
intranet application or their management application
that they use for their customers and things

98
00:06:41,528 --> 00:06:44,448
like that. And I was just there. That was Postgres

99
00:06:45,408 --> 00:06:46,488
live and,

100
00:06:47,668 --> 00:06:51,408
you know, then I was
programming Perl, PHP stuff, and

101
00:06:52,068 --> 00:06:55,168
did logged into Postgres and created
tables and that kind of thing.

102
00:06:56,290 --> 00:07:00,090
[CLAIRE] Do you, do you remember what version
of Postgres was the most recent at the time,

103
00:07:00,150 --> 00:07:02,490
or what year are we talking about exactly?

104
00:07:04,068 --> 00:07:05,008
[PETER] Yeah, that was,

105
00:07:05,388 --> 00:07:08,168
it was 1999,

106
00:07:10,808 --> 00:07:14,388
and it would have been Postgres
6.4, 6.5 or something like that.

107
00:07:14,427 --> 00:07:17,288
It was before 7, so because later
on, I guess we'll get to that in a

108
00:07:17,328 --> 00:07:21,768
minute, then I got involved in the development,
and so the next big milestone was Postgres

109
00:07:22,168 --> 00:07:22,928
7.0.

110
00:07:23,668 --> 00:07:28,468
And so at the time we were using 6.4,
it was before foreign keys, I remember.

111
00:07:29,448 --> 00:07:31,208
So I think it was probably that, yeah.

112
00:07:35,270 --> 00:07:41,390
[CLAIRE] I am curious if you remember what
your first contribution was to Postgres.

113
00:07:43,370 --> 00:07:46,450
I don't know if you dug it up,
if you have a link to the commit,

114
00:07:48,390 --> 00:07:53,310
and was that also in the same
time frame? Was it, you said 1999,

115
00:07:53,790 --> 00:07:55,810
is that also when you made
your first contribution?

116
00:07:57,448 --> 00:08:01,788
[PETER] Yeah, I mean, exactly, right. I got
into the hacking on Postgres pretty quickly

117
00:08:02,288 --> 00:08:05,268
because I probably apparently had a
lot of time on my hand at the time.

118
00:08:05,348 --> 00:08:08,208
You know, I was in college and it didn't...

119
00:08:09,168 --> 00:08:12,908
I chose to spend my time that
way, I suppose, right? But

120
00:08:13,568 --> 00:08:16,808
I got into it really in the, at the time, the

121
00:08:17,308 --> 00:08:20,448
traditional way of scratching your own
itch, as we like to say at the time.

122
00:08:21,348 --> 00:08:25,548
That I was using the system, I didn't
like a specific aspect of it, and then

123
00:08:25,748 --> 00:08:28,588
I sort of dug into it and see if I could fix it.

124
00:08:30,548 --> 00:08:34,368
I'm not sure if this was literally the
first patch I sent, but the first...

125
00:08:34,831 --> 00:08:39,908
the real piece of functionality that I
worked on was the tab completion in psql.

126
00:08:41,048 --> 00:08:42,068
Is that at the time,

127
00:08:42,648 --> 00:08:46,188
you sort of have this reflex that when
you use a shell, you press Tab all

128
00:08:46,208 --> 00:08:47,288
the time, and in a

129
00:08:48,368 --> 00:08:52,228
shell that works, but in psql at the
time, it didn't do anything useful.

130
00:08:53,688 --> 00:08:56,968
It actually thought it was a shell, like
a Unix shell, and just gave you nonsense

131
00:08:57,008 --> 00:08:59,588
completions. And that I thought, well, I, that...

132
00:09:00,288 --> 00:09:02,268
doesn't make sense. I think
maybe we can do better.

133
00:09:02,948 --> 00:09:06,608
I had no idea at the time if I
could succeed in that, but somehow

134
00:09:07,888 --> 00:09:10,188
over the summer, several weeks, I...

135
00:09:11,068 --> 00:09:13,808
so figured it out. So I think that
was my first substantial contribution.

136
00:09:13,828 --> 00:09:17,048
There might have been one or two sort of
small commits before that, if you look

137
00:09:17,088 --> 00:09:20,848
into the records, but I think
that's really where I started as a

138
00:09:21,728 --> 00:09:24,228
feature that I really wanted for myself.

139
00:09:25,328 --> 00:09:26,288
And that was substantial.

140
00:09:27,830 --> 00:09:29,690
[CLAIRE] And from there, how did it evolve?

141
00:09:32,150 --> 00:09:37,170
Melanie Plageman has always persuaded me
to focus on what made you keep coming back?

142
00:09:37,270 --> 00:09:41,530
Why did you keep coming back? So what
were the next steps in your story?

143
00:09:42,608 --> 00:09:45,608
[PETER] Yeah, I think there was a
combination of things. I think one was,

144
00:09:46,588 --> 00:09:52,868
I think I was apparently somewhat good
at it, right? My contributions were

145
00:09:53,648 --> 00:09:55,088
well received and so on, and

146
00:10:03,768 --> 00:10:05,168
it was a community of

147
00:10:05,688 --> 00:10:09,388
people I didn't know at the time,
but it was just a place to hang out

148
00:10:09,468 --> 00:10:09,708
and

149
00:10:10,628 --> 00:10:11,968
contribute and do something.

150
00:10:14,268 --> 00:10:17,308
You know, I think my roommates at the
time, they were going playing laser tag or

151
00:10:17,348 --> 00:10:20,388
something and I was doing this instead.

152
00:10:22,770 --> 00:10:26,390
[CLAIRE] Oh no, you could have been
like an Olympian laser tag player.

153
00:10:27,708 --> 00:10:30,887
[PETER] I did do some laser tag, but
I divided my time wisely, I think.

154
00:10:32,128 --> 00:10:37,208
But yeah, and once you start digging,
why, at the time it was the quality of

155
00:10:37,268 --> 00:10:38,548
the code at the time was

156
00:10:39,808 --> 00:10:41,788
dubious in various places, and then you can,

157
00:10:43,968 --> 00:10:45,448
as you dig around, you find more things.

158
00:10:45,468 --> 00:10:48,328
Oh, I could fix this, or I can
improve that. I can improve that.

159
00:10:48,568 --> 00:10:50,668
And again, so it's snowballed from that, right?

160
00:10:51,808 --> 00:10:53,028
The things you do,

161
00:10:54,448 --> 00:10:54,808
people

162
00:10:55,708 --> 00:10:56,908
welcome them somehow, right?

163
00:10:58,008 --> 00:11:00,828
People welcome you, and then you find it useful.

164
00:11:00,888 --> 00:11:03,888
I was using the system as well at
the time, of course, and so I was

165
00:11:03,948 --> 00:11:05,348
trying to also improve it for my own work.

166
00:11:06,348 --> 00:11:08,028
And then you just goes on and on and,

167
00:11:09,288 --> 00:11:09,848
yeah, but then

168
00:11:11,088 --> 00:11:11,508
keep going.

169
00:11:12,210 --> 00:11:14,450
[CLAIRE] And then you continued
to work for that same company?

170
00:11:16,308 --> 00:11:18,728
[PETER] No, actually, I didn't work for
that. It was just a summer internship.

171
00:11:18,808 --> 00:11:20,528
So in a way, this was kind of,

172
00:11:22,028 --> 00:11:26,508
I hopped around at the time quite a bit
because I was also moving between different

173
00:11:26,548 --> 00:11:30,808
countries because of the sort of
semester abroad type of things and then

174
00:11:32,468 --> 00:11:36,248
interrupted university for a little while to
do something else, but I could always do the

175
00:11:36,288 --> 00:11:37,708
Postgres work. That was sort of

176
00:11:38,508 --> 00:11:42,148
a hobby, a community I could
just keep going across different

177
00:11:43,668 --> 00:11:48,648
locations and things like that, which also was
a, nowadays maybe that's kind of standard, right?

178
00:11:48,728 --> 00:11:49,828
But at the time that was,

179
00:11:50,788 --> 00:11:54,108
a newish thing that you had sort
of online hobbies that you could

180
00:11:54,968 --> 00:11:56,568
just keep going. So I was I...

181
00:11:57,608 --> 00:11:58,748
popped up in a new place,

182
00:11:59,988 --> 00:12:01,448
new country, and then I say, well

183
00:12:02,308 --> 00:12:04,028
everything is new here, but I can do this, right?

184
00:12:04,148 --> 00:12:06,088
I can keep going with these
people that I know online.

185
00:12:08,310 --> 00:12:10,270
[CLAIRE] Why were you
changing countries, can I ask?

186
00:12:11,290 --> 00:12:12,690
Is there some dramatic story?

187
00:12:11,508 --> 00:12:14,908
[PETER] Oh, this was just my...
no, this was just college, right?

188
00:12:14,988 --> 00:12:18,388
You want to do a semester abroad
here, and then for a while I was back

189
00:12:18,408 --> 00:12:21,768
home. I was studying in the... when I
got started, I was living in Michigan.

190
00:12:23,668 --> 00:12:25,188
And then I was in Sweden.

191
00:12:27,648 --> 00:12:29,748
Then I was back home in Germany for a while.

192
00:12:30,208 --> 00:12:33,568
Then I was back in the U.S.
So I for the way just the

193
00:12:34,028 --> 00:12:38,528
my sort of college curriculum worked out,
I was in a bunch of different places.

194
00:12:39,688 --> 00:12:42,088
Different years, but I could
always keep doing this.

195
00:12:43,640 --> 00:12:48,640
[CLAIRE] Got it. So Postgres was the one constant
in your life at the time, besides family.

196
00:12:48,468 --> 00:12:50,788
[PETER] Yeah, yeah, pretty much, yeah.

197
00:12:51,800 --> 00:12:56,900
[CLAIRE] Nice. When did you first start
meeting people in the Postgres community?

198
00:12:57,320 --> 00:13:01,280
Did you, did you work online with them
for years and years and years before you

199
00:13:01,340 --> 00:13:02,560
ever met someone in person?

200
00:13:05,308 --> 00:13:07,668
[PETER] Yeah, for a while, because we didn't have

201
00:13:08,688 --> 00:13:11,108
conferences as we do now, right?

202
00:13:11,828 --> 00:13:12,828
The first

203
00:13:14,348 --> 00:13:18,748
event that I went to was FOSDEM 2003,

204
00:13:19,968 --> 00:13:23,708
which I think by some standards is
probably the first ever Postgres event.

205
00:13:23,768 --> 00:13:27,408
Maybe somewhere else before that two people
met in a bar and talked about Postgres, right?

206
00:13:27,468 --> 00:13:31,788
But this was the first event with
Postgres on the schedule, I think, 2003.

207
00:13:32,868 --> 00:13:35,808
Bruce Momjian was there,
who is still of course now

208
00:13:36,428 --> 00:13:40,588
famous, but at the time really community
leader and the first who really went out, did

209
00:13:40,808 --> 00:13:41,968
conference talks and so on, and

210
00:13:43,228 --> 00:13:44,648
he ran

211
00:13:46,068 --> 00:13:49,148
the dev room, as we say
now, at FOSDEM in 2003. And

212
00:13:49,688 --> 00:13:52,108
so I met him, met a bunch of
other people I knew from online.

213
00:13:54,448 --> 00:13:58,468
Met Michael Meskes, who also then
gave me my first Postgres job.

214
00:13:59,768 --> 00:14:01,068
And all then went from there.

215
00:14:02,600 --> 00:14:05,600
[CLAIRE] And where was your first Postgres
job? Where and when did that happen?

216
00:14:06,688 --> 00:14:12,028
[PETER] So after that, I
started working at Credativ,

217
00:14:12,048 --> 00:14:14,668
a German company that is still around today.

218
00:14:15,588 --> 00:14:16,168
We were doing.

219
00:14:17,228 --> 00:14:22,668
Well, this is a consulting company around
open source in general, I would say.

220
00:14:23,388 --> 00:14:28,408
Postgres wasn't really a business yet
at the time, but we kind of built it up.

221
00:14:30,308 --> 00:14:34,428
So maybe did I, again, other people might
have done similar things at the same time,

222
00:14:34,488 --> 00:14:35,368
but I think we did

223
00:14:36,128 --> 00:14:41,508
one of the first training courses for Postgres that
was commercially available and things like that.

224
00:14:44,300 --> 00:14:48,560
[CLAIRE] One of the things that a previous
guest on the podcast reflected on is that,

225
00:14:49,220 --> 00:14:53,340
or maybe they didn't say, but I reflected
on it as I listened to their stories,

226
00:14:53,800 --> 00:14:54,720
is that part of

227
00:14:56,080 --> 00:15:00,480
A lot of people's career paths is,
when you look back, it's saying yes

228
00:15:01,200 --> 00:15:02,800
to opportunities that come along.

229
00:15:03,080 --> 00:15:06,560
You know how if you're happy with what
you're doing and someone comes along and they

230
00:15:07,460 --> 00:15:13,580
offer you something, it's very easy to say
no because it's, right, it's an unknown.

231
00:15:13,660 --> 00:15:16,440
You don't know what's going to happen
over there. You're happy where you are.

232
00:15:16,560 --> 00:15:18,100
Why would you even have the conversation?

233
00:15:19,240 --> 00:15:23,040
But as I talked to people, I realized
they got these out of the blue or

234
00:15:23,100 --> 00:15:26,480
out of left field or these opportunities,
and they embraced them and they said yes.

235
00:15:26,840 --> 00:15:30,680
So I don't know if you feel
like that happened to you.

236
00:15:31,340 --> 00:15:35,520
Was saying yes important in this
whole 25-year journey or not?

237
00:15:38,328 --> 00:15:42,708
[PETER] Probably also, but I think
especially in the early half.

238
00:15:43,948 --> 00:15:47,948
It wasn't so much that opportunities just
show up and you have to take them, right?

239
00:15:48,008 --> 00:15:50,368
You really have to search them
or make them yourself, right?

240
00:15:50,448 --> 00:15:52,708
It's not like if you want
a Postgres job now, you can

241
00:15:53,508 --> 00:15:55,968
find one somewhere, or at
least you know where to look.

242
00:15:57,908 --> 00:15:59,248
Back then, that didn't really exist.

243
00:16:00,028 --> 00:16:01,128
Right, we had to sort of

244
00:16:02,728 --> 00:16:03,668
decide to do that,

245
00:16:04,368 --> 00:16:08,028
or you sort of have to find that
this is even a possibility, I think.

246
00:16:09,560 --> 00:16:14,640
[CLAIRE] So with the Credativ job in
Germany, is that one that you then sought out

247
00:16:15,100 --> 00:16:17,560
and had to persuade and sell yourself into?

248
00:16:18,268 --> 00:16:22,268
[PETER] And not so much persuade
but I reached out, right.

249
00:16:23,308 --> 00:16:25,708
I was, I was not contacted. I reached out.

250
00:16:27,700 --> 00:16:28,780
[CLAIRE] And obviously it worked.

251
00:16:27,988 --> 00:16:32,168
[PETER] Because we didn't, we didn't
know each other really. It's not like

252
00:16:32,908 --> 00:16:37,528
we've ran into each other before or anything
like that. We didn't even know, what...

253
00:16:38,448 --> 00:16:40,348
We just knew names on an email.

254
00:16:41,288 --> 00:16:43,668
Right. Not even, you didn't even have

255
00:16:44,268 --> 00:16:48,768
what you could do now, go into someone's
LinkedIn page and see what their story is

256
00:16:48,868 --> 00:16:52,188
or something like that, right? You
just had names on a mailing list and

257
00:16:53,208 --> 00:16:55,688
didn't know if they were like
nice people or scary, right?

258
00:16:57,388 --> 00:16:57,888
So actually,

259
00:16:58,928 --> 00:17:01,908
in many of those cases, just
contacting someone personally was

260
00:17:02,408 --> 00:17:05,688
very sort of weird in a way because you
didn't know who you were talking to.

261
00:17:05,968 --> 00:17:09,588
It's just a name that is reflected
by just emails you've read over time.

262
00:17:10,728 --> 00:17:12,168
It's quite different from now, I would say.

263
00:17:12,640 --> 00:17:14,120
[CLAIRE] And there was no LinkedIn, right?

264
00:17:15,868 --> 00:17:19,808
[PETER] No, definitely not. I don't
know when that would have started. Was

265
00:17:19,700 --> 00:17:23,480
[CLAIRE] I feel like it was 2005-ish.

266
00:17:20,428 --> 00:17:23,168
[PETER] even before Facebook or before...

267
00:17:24,268 --> 00:17:28,068
yeah, so definitely much before that.
I don't even know how you would,

268
00:17:29,108 --> 00:17:30,868
know anything about anyone.

269
00:17:33,028 --> 00:17:35,328
You know, in those days. I mean,
unless they had a website, I guess

270
00:17:35,948 --> 00:17:36,388
some people did.

271
00:17:37,000 --> 00:17:41,000
[CLAIRE] Okay, so you went from Credativ in
Germany, and you were there for like five years,

272
00:17:41,440 --> 00:17:45,480
and that's when you went to my
favorite company, Sun Microsystems.

273
00:17:46,228 --> 00:17:46,448
[PETER] Yeah.

274
00:17:47,500 --> 00:17:50,400
[CLAIRE] And I had already left Sun by that point.

275
00:17:51,740 --> 00:17:55,200
I was long gone, but you worked
there in Finland, is that right?

276
00:17:56,128 --> 00:18:01,249
[PETER] That's correct. I moved to Finland
for family reasons, and so in a way I

277
00:18:01,848 --> 00:18:04,168
needed a new job, and then I just,

278
00:18:05,468 --> 00:18:08,348
this... how did this contact get
made? Probably at a conference.

279
00:18:08,688 --> 00:18:11,488
At the time, we did have then
conferences, and it was possible to

280
00:18:12,396 --> 00:18:14,436
make contact with other people and so on, so.

281
00:18:15,256 --> 00:18:17,896
I got the, I got the job at Sun,

282
00:18:18,416 --> 00:18:22,896
who had a Postgres business at the time,
which then didn't last much longer after that.

283
00:18:22,976 --> 00:18:25,516
And so I wasn't staying there very long,
but it was super interesting there.

284
00:18:27,156 --> 00:18:27,896
It's such a...

285
00:18:29,576 --> 00:18:33,176
learned a lot there about
just the technology industry.

286
00:18:35,056 --> 00:18:38,636
It's quite, I feel it's quite unfortunate
that it sort of is forgotten now.

287
00:18:38,776 --> 00:18:40,836
I wish they would write a book
about Sun or something like that.

288
00:18:40,876 --> 00:18:41,796
I don't know, maybe there's one.

289
00:18:42,950 --> 00:18:47,710
[CLAIRE] Oh, there probably is one. Your,
yeah, your description on LinkedIn today

290
00:18:48,170 --> 00:18:50,670
is a little, I don't know, is
tongue in cheek the right word?

291
00:18:51,030 --> 00:18:54,350
You say assisted in the demise
of a Silicon Valley pioneer.

292
00:18:55,970 --> 00:18:57,990
That's so sad. It's so sad.

293
00:18:58,070 --> 00:19:01,809
You know, when I first started working
at Sun, it was like the hottest place to

294
00:19:01,849 --> 00:19:02,110
work.

295
00:19:02,590 --> 00:19:05,070
And so I would tell people I worked
there, and you could tell them do a

296
00:19:05,110 --> 00:19:09,290
double take, like, Oh my gosh, you
work for Sun? And that was really cool.

297
00:19:09,310 --> 00:19:12,690
And then, of course, years and years later,
people would find out that you worked there

298
00:19:12,710 --> 00:19:15,990
and they'd be like, Oh, you
worked for Sun, right? The whole

299
00:19:16,470 --> 00:19:19,010
same words, but completely
different tone of voice.

300
00:19:21,050 --> 00:19:26,250
So, but I'm glad we have that in common.
And you worked on Postgres there too.

301
00:19:26,570 --> 00:19:31,530
And then you went from there to a company
that I'm not familiar with called F-Secure.

302
00:19:32,090 --> 00:19:37,470
And after that, oh my gosh, MeetMe,
and eventually 2ndQuadrant and EDB.

303
00:19:37,656 --> 00:19:38,956
[PETER] That's right. That's right.

304
00:19:38,450 --> 00:19:41,830
[CLAIRE] And Postgres is the common
thread through all of those jobs?

305
00:19:41,416 --> 00:19:46,976
[PETER] Yes, F-Secure and MeetMe were
users of Postgres, also community sponsors,

306
00:19:47,556 --> 00:19:53,096
but not developers, right, themselves,
but users. I was doing DBA work and some

307
00:19:53,996 --> 00:19:55,656
Postgres hacking on the side mostly, and then

308
00:19:56,536 --> 00:19:57,856
with 2ndQuadrant, it was,

309
00:19:59,296 --> 00:20:01,996
also, I reached out in that
case, right, 2ndQuadrant.

310
00:20:02,530 --> 00:20:06,470
[CLAIRE] Okay, so you didn't just have opportunities
thrown at your feet your whole career is what

311
00:20:06,490 --> 00:20:06,850
you're saying.

312
00:20:07,376 --> 00:20:08,756
[PETER] Well, you know, there have been,

313
00:20:11,216 --> 00:20:12,356
there have been opportunities.

314
00:20:13,276 --> 00:20:18,956
Over time, probably, I don't remember specifics
now, but people had contacted me from time to

315
00:20:18,996 --> 00:20:20,356
time also, but

316
00:20:21,735 --> 00:20:24,936
for whatever reason. So maybe I was
more like you said, like saying no.

317
00:20:25,016 --> 00:20:28,756
What did you say? Saying no is
easy, maybe, or saying no is hard.

318
00:20:29,590 --> 00:20:36,230
[CLAIRE] I, it's words are so tricky.
It's actually difficult to say no to like

319
00:20:37,490 --> 00:20:40,130
ideas for features, or it...

320
00:20:41,150 --> 00:20:44,830
people come to you for help,
and you want to help them.

321
00:20:45,010 --> 00:20:46,890
And so you say yes, even if you don't have time.

322
00:20:47,150 --> 00:20:50,410
So sometimes saying no is actually
easy, but sometimes it's hard.

323
00:20:50,430 --> 00:20:52,870
And I don't know what I was
talking about. Forget it.

324
00:20:53,010 --> 00:20:55,150
Forget I ever said anything, because...

325
00:20:56,336 --> 00:20:58,076
[PETER] No, but that's actually,
that's actually right, right.

326
00:20:58,136 --> 00:21:01,436
It's in some cases you sort of default to

327
00:21:02,696 --> 00:21:05,076
a certain direction that's
maybe not of advantage to you.

328
00:21:06,070 --> 00:21:12,310
[CLAIRE] For me, career-wise, I have not
said yes enough. I have turned down some

329
00:21:12,770 --> 00:21:18,210
fantastic opportunities, and I think at the
end of the day, it's because I was resistant

330
00:21:18,250 --> 00:21:22,130
to change, and it was just easier to
stay where I was. And I was happy.

331
00:21:22,710 --> 00:21:25,790
I was happy where I was. And then I remember Tom

332
00:21:26,350 --> 00:21:28,730
Lane talking about how he had

333
00:21:29,650 --> 00:21:32,890
it nowhere in his mind that he
was going to end up in software.

334
00:21:33,450 --> 00:21:37,190
And a professor came along to him and
said, You should really TA this class.

335
00:21:37,810 --> 00:21:42,490
You're really good at this.
Or maybe it was become a

336
00:21:42,990 --> 00:21:46,830
summer researcher or something
like that. And he said yes.

337
00:21:47,670 --> 00:21:51,250
It wasn't his plan. It wasn't his intention,
and he said yes to that opportunity.

338
00:21:51,330 --> 00:21:53,450
So that's kind of what I was thinking of. And

339
00:21:54,410 --> 00:21:56,590
I was wondering if you'd
had those opportunities too.

340
00:21:55,856 --> 00:21:58,396
[PETER] Yeah, that, I think that very first

341
00:21:59,556 --> 00:22:02,096
job at the ISP, the internship.

342
00:22:03,116 --> 00:22:04,696
I was asked and

343
00:22:05,496 --> 00:22:08,336
I was not prepared for that, right? So I had to

344
00:22:09,116 --> 00:22:11,396
actually say, okay, sure, I'll do that.

345
00:22:11,456 --> 00:22:13,496
I don't know what you're asking, but I'll do it.

346
00:22:15,050 --> 00:22:15,730
[CLAIRE] I'll figure it out.

347
00:22:15,176 --> 00:22:18,076
[PETER] I mean, at the time, at the time,
I didn't really have anything else to do,

348
00:22:18,176 --> 00:22:20,636
so that was in a way easy. But it was,

349
00:22:21,956 --> 00:22:23,196
I also could have just said, no, I'll...

350
00:22:24,676 --> 00:22:28,116
don't know what you're talking about. I'd
rather, you know, watch TV or something. So,

351
00:22:30,236 --> 00:22:33,236
over the summer, it was a summer internship,
so I could have chosen to do something

352
00:22:33,316 --> 00:22:36,796
else. But I was like, sure,
yeah. I mean, these were sort of

353
00:22:37,356 --> 00:22:41,416
private contacts, you know, people I kind
of knew and so on, so that probably helped.

354
00:22:43,090 --> 00:22:48,009
[CLAIRE] I think one of the challenges
talking about 25 years in an industry

355
00:22:48,610 --> 00:22:52,850
is I sometimes feel for me that
I've forgotten more than I remember.

356
00:22:53,010 --> 00:22:53,690
You know what I mean?

357
00:22:53,730 --> 00:22:58,330
There's so much has happened in a 25-year
period that it's actually quite hard

358
00:22:58,790 --> 00:23:01,790
to pick out, to cherry-pick
a few interesting stories.

359
00:23:02,090 --> 00:23:05,570
But that's exactly what I'm going to
ask you to do, is to cherry-pick a few

360
00:23:05,336 --> 00:23:08,216
[PETER] Yeah, but you can look at all my

361
00:23:05,630 --> 00:23:06,650
[CLAIRE] interesting stories.

362
00:23:08,816 --> 00:23:13,296
[PETER] emails that I've written publicly that
are archived, and you can go into the metadata and

363
00:23:13,356 --> 00:23:15,336
see when I've sent them and from where.

364
00:23:16,356 --> 00:23:18,896
And then that probably tells a lot of the story.

365
00:23:19,556 --> 00:23:21,276
I've never done this myself,
but you could probably

366
00:23:21,836 --> 00:23:25,816
look at some point I changed from posting
at night to posting during the day or

367
00:23:25,856 --> 00:23:26,716
something like that, right?

368
00:23:28,790 --> 00:23:33,170
[CLAIRE] Is this like the Postgres
hackers equivalent of Googling yourself

369
00:23:33,890 --> 00:23:38,470
is going and querying the hackers
mailing list to see the patterns.

370
00:23:38,136 --> 00:23:43,096
[PETER] No, but I think there is, there
are, I think there are patterns of, in the

371
00:23:43,976 --> 00:23:46,036
early part of my career or in early,

372
00:23:46,896 --> 00:23:49,456
sort of early life of Postgres,
the community, there's

373
00:23:50,016 --> 00:23:53,096
probably most people were hobbyists of some sort,

374
00:23:53,916 --> 00:23:56,016
or they did it after work or something like that.

375
00:23:57,256 --> 00:23:58,836
And so they would, when they posted,

376
00:23:59,496 --> 00:24:03,556
you know, their patches or their reviews
or discussions, they would do it at 11 p.m.

377
00:24:03,596 --> 00:24:07,716
their time. And then at some point this changed to

378
00:24:08,916 --> 00:24:12,936
as you know, most people now do
it as a job, and so you do, you

379
00:24:13,036 --> 00:24:15,836
do your posting, you know, at 10 a.m.

380
00:24:15,750 --> 00:24:16,750
[CLAIRE] During the day, yeah.

381
00:24:16,588 --> 00:24:20,708
[PETER] And then you don't do, and then Saturday,
Sunday, you don't post anything or very little.

382
00:24:20,968 --> 00:24:23,668
I think there is, if somebody
wants to do this analysis,

383
00:24:24,487 --> 00:24:25,848
I think this is probably true.

384
00:24:26,750 --> 00:24:32,130
[CLAIRE] Unless you made a mistake on Friday
or Thursday, in which case I imagine you are

385
00:24:32,190 --> 00:24:33,990
saying something on Saturday and Sunday.

386
00:24:34,728 --> 00:24:38,768
[PETER] That is, that also happens a few
times and then you don't do it anymore.

387
00:24:40,348 --> 00:24:42,488
No, there was actually a time when...

388
00:24:43,948 --> 00:24:47,048
this now goes into all the
inside baseball, but, you know,

389
00:24:48,228 --> 00:24:52,808
it's sort of when you, when you commit
something, the buildfarm runs, like, a lot of

390
00:24:52,868 --> 00:24:53,988
you will know that, and then

391
00:24:54,948 --> 00:24:57,328
the buildfarm may or may not
accept what you've committed.

392
00:24:58,708 --> 00:25:02,968
And for a while it was, some
years ago, it was really

393
00:25:04,308 --> 00:25:04,968
bad that.

394
00:25:05,968 --> 00:25:09,228
I guess we didn't have enough sort of
test coverage ahead of time, so there was

395
00:25:09,268 --> 00:25:11,808
always a fairly significant risk, even if you did

396
00:25:12,608 --> 00:25:16,108
everything you could locally, that there
would be some kind of build form failure.

397
00:25:17,028 --> 00:25:20,628
At some point, it's got so bad that
I said to myself, I'm not even, not

398
00:25:20,708 --> 00:25:26,468
even Friday, we're talking about Friday weekend
work. I'm not even gonna commit anything afternoon,

399
00:25:26,468 --> 00:25:29,108
because I don't want to work
into the night to fix it.

400
00:25:30,128 --> 00:25:32,668
It's not so bad anymore now, but
it is a lesson I've learned also.

401
00:25:33,488 --> 00:25:37,288
Don't deploy on Friday, but don't commit
in the afternoon or in the evening.

402
00:25:37,758 --> 00:25:39,098
[CLAIRE] On any day of the week, you mean.

403
00:25:40,348 --> 00:25:43,208
[PETER] More or less, yeah.
It's gotten a lot better now.

404
00:25:43,718 --> 00:25:45,098
[CLAIRE] Are you a morning
person or a night person?

405
00:25:47,088 --> 00:25:50,528
[PETER] I have turned into
a morning person by force.

406
00:25:50,748 --> 00:25:53,408
Again, someone could do this
analysis, but I think in

407
00:25:54,368 --> 00:25:57,228
the early times I probably worked
into the night, through the night.

408
00:25:58,108 --> 00:26:00,988
Now I work, you know, in normal
workday for the most part.

409
00:26:01,768 --> 00:26:06,908
Try to get most of the thinking
and developing work done in the

410
00:26:07,748 --> 00:26:10,268
before noon and then in the
afternoons it's all meetings.

411
00:26:10,658 --> 00:26:10,998
[CLAIRE] Okay, what?

412
00:26:11,978 --> 00:26:12,918
What caused that change?

413
00:26:13,338 --> 00:26:16,718
What do you mean you forced yourself to
switch from being a night person to being

414
00:26:16,068 --> 00:26:21,308
[PETER] Because I have a family now and not
just a sort of a lonesome college student.

415
00:26:16,738 --> 00:26:17,298
[CLAIRE] a morning person?

416
00:26:22,638 --> 00:26:22,978
Got it.

417
00:26:23,318 --> 00:26:26,558
So you want to be able to spend time
with your family in the evenings and

418
00:26:26,618 --> 00:26:29,038
not be cleaning up from the days.

419
00:26:27,848 --> 00:26:31,488
[PETER] Yeah, you know, you just do a
eight to five, nine to five type of job,

420
00:26:31,528 --> 00:26:33,228
and then there's, you know,

421
00:26:34,128 --> 00:26:36,448
time for the family and the usual things that

422
00:26:37,088 --> 00:26:37,448
we'll do.

423
00:26:38,638 --> 00:26:43,378
[CLAIRE] And you're making a special exception for
today's podcast episode, I take it, because it is

424
00:26:43,478 --> 00:26:45,258
after five o'clock where you are, right?

425
00:26:46,048 --> 00:26:46,548
[PETER] It is, yes.

426
00:26:46,608 --> 00:26:50,968
I mean, the reality of things is that
sometimes you have to take evenings now to

427
00:26:52,028 --> 00:26:52,748
talk to, you know,

428
00:26:53,948 --> 00:26:57,068
such as now, or to talk to colleagues
overseas and things like that.

429
00:26:57,108 --> 00:26:58,528
So you have to be a little bit flexible, but

430
00:27:00,268 --> 00:27:02,568
I schedule and plan those kinds of things.

431
00:27:04,558 --> 00:27:08,958
[CLAIRE] I've never figured out how to make
myself a morning person. I raised kids, and

432
00:27:09,698 --> 00:27:14,578
lucky for me, they were good sleepers. They
would sleep in the mornings too. So, yeah,

433
00:27:14,988 --> 00:27:16,668
[PETER] But I have to be up. I have to be

434
00:27:15,318 --> 00:27:15,678
[CLAIRE] I haven't.

435
00:27:17,228 --> 00:27:20,588
[PETER] the first one up to get them up.
Otherwise, nothing will happen in the morning.

436
00:27:22,498 --> 00:27:23,458
[CLAIRE] Got it. Okay.

437
00:27:25,878 --> 00:27:26,138
All right.

438
00:27:26,358 --> 00:27:31,318
So the common thread across these 25 years, across
all these different companies, was Postgres.

439
00:27:32,798 --> 00:27:38,858
Have there been... are there stories? Can you
cherry-pick us some stories that help us understand

440
00:27:39,678 --> 00:27:42,798
a little bit about what it's been like to grow?

441
00:27:43,238 --> 00:27:46,278
I mean, what's interesting is
as your career has flourished

442
00:27:46,958 --> 00:27:52,698
working in Postgres, and as the scope of
responsibility that you've taken on has expanded, the

443
00:27:52,738 --> 00:27:56,838
Postgres project has grown like
gangbusters too, right? So...

444
00:27:58,298 --> 00:28:02,998
you've been growing on top of this
tidal wave, if you will, of a project.

445
00:28:04,468 --> 00:28:07,988
[PETER] Yeah, exactly. So,
yeah, I happened to be sort of

446
00:28:08,568 --> 00:28:11,308
in on the ground floor, I guess,
a little bit, right, and then it

447
00:28:11,948 --> 00:28:13,748
grew, which was fortunate.

448
00:28:16,428 --> 00:28:19,248
But yeah, it has, it has changed, right?

449
00:28:19,308 --> 00:28:21,428
Initially, as I said, I started as a user.

450
00:28:22,608 --> 00:28:23,228
And most

451
00:28:23,928 --> 00:28:28,368
developers were users, and there was
this mailing list culture where you,

452
00:28:29,088 --> 00:28:31,888
sort of everybody was on, you know,
either on a hackers mailing list or on a

453
00:28:31,928 --> 00:28:34,868
general mailing list, and that was sort of the
whole universe of people who were interested

454
00:28:34,887 --> 00:28:37,267
in Postgres, and you got a
lot of direct feedback also.

455
00:28:38,068 --> 00:28:42,308
When I was doing initially training, consulting,
you talk to users directly, you get feedback, and

456
00:28:42,368 --> 00:28:42,768
you really

457
00:28:43,428 --> 00:28:47,908
had this sort of idea that was very prominent
initially in open source, that you get

458
00:28:47,948 --> 00:28:51,288
sort of the direct feedback loops
and make good products that way.

459
00:28:52,028 --> 00:28:52,408
And then

460
00:28:53,228 --> 00:28:55,048
over time, as things have grown, right, you...

461
00:28:56,108 --> 00:28:57,108
it's hard to really

462
00:28:58,708 --> 00:29:02,248
keep that contact and keep your,
how do you say, sort of your

463
00:29:03,188 --> 00:29:07,908
eye on what the users want and so on,
because it's so disintermediated now that

464
00:29:08,608 --> 00:29:09,028
we have

465
00:29:10,948 --> 00:29:12,788
in companies, right, you have, you would

466
00:29:13,328 --> 00:29:15,068
have a development organization, you have

467
00:29:15,548 --> 00:29:18,188
field organizations, and they're
very big and, of course you,

468
00:29:18,888 --> 00:29:22,428
part of your job to really stay on top
of that, but it's much more difficult

469
00:29:22,468 --> 00:29:22,588
and

470
00:29:23,488 --> 00:29:26,748
goes through so many different hops and so
on, so it's quite a different situation.

471
00:29:26,788 --> 00:29:29,768
And then also, as you're saying, right, in the
community, there's so many more responsibilities

472
00:29:31,148 --> 00:29:33,488
to organize things and manage things and so on.

473
00:29:35,848 --> 00:29:37,668
Very little time to do all of these things.

474
00:29:40,998 --> 00:29:44,418
[CLAIRE] I know I introduced you in the
beginning, and I spoke about a bunch of your

475
00:29:44,458 --> 00:29:47,178
different responsibilities,
but I guess I'd like you to

476
00:29:47,898 --> 00:29:52,558
walk us through the different ways
you contribute to the project.

477
00:29:52,838 --> 00:29:54,438
When you think of the top.

478
00:29:55,138 --> 00:29:59,638
Five different categories of ways that you're
participating in Postgres. What are they?

479
00:30:02,068 --> 00:30:05,768
[PETER] Well, the development, I
tried to go to, I tried to do some

480
00:30:07,148 --> 00:30:08,848
blogging and things like that, right?

481
00:30:09,588 --> 00:30:11,248
Which I also should do more, but

482
00:30:12,508 --> 00:30:14,008
I like doing that, explaining things.

483
00:30:15,028 --> 00:30:16,348
You know, why you do,

484
00:30:18,040 --> 00:30:21,340
what the ideas were behind what you've done,
you know, obviously you want to promote your

485
00:30:21,400 --> 00:30:23,980
work a little bit if you implemented a feature.

486
00:30:25,400 --> 00:30:30,680
Also just sort of ideas and sometimes gather
feedback that way. So I think that's useful.

487
00:30:34,300 --> 00:30:38,460
I guess people know that I'm in the
core team. The core team itself doesn't

488
00:30:39,340 --> 00:30:41,200
do nearly as much as people think

489
00:30:42,000 --> 00:30:42,980
it does, probably.

490
00:30:44,020 --> 00:30:46,740
It is mostly a place where
things get delegated out of,

491
00:30:47,560 --> 00:30:47,720
right?

492
00:30:49,540 --> 00:30:52,520
All of these bodies that exist now, the
release team, the security team, and

493
00:30:54,120 --> 00:30:58,120
code of conduct team effectively and things
like that were just delegated out of the core

494
00:30:58,160 --> 00:30:58,360
team.

495
00:30:59,408 --> 00:31:03,808
[CLAIRE] So just to pause for a split second,
for anyone listening who has not heard the

496
00:31:03,848 --> 00:31:09,128
term core team before in Postgres, in other open
source projects, sometimes there is a project

497
00:31:09,228 --> 00:31:15,088
steering committee. So that's an equivalent
term across the open source community, and

498
00:31:16,388 --> 00:31:19,068
I think there are about seven
people on the Postgres core team,

499
00:31:19,688 --> 00:31:25,068
and explicitly from different companies. I
think it's probably part of the charter that

500
00:31:20,060 --> 00:31:20,560
[PETER] Seven, yeah.

501
00:31:26,428 --> 00:31:31,328
[CLAIRE] you can't have more than a certain number
of people from the same company because Postgres,

502
00:31:31,788 --> 00:31:35,308
as a project, does not belong
to any one corporate entity.

503
00:31:35,388 --> 00:31:39,348
It's contributed to from lots of different
places and companies and countries.

504
00:31:40,368 --> 00:31:41,648
There. Did I summarize that right?

505
00:31:42,780 --> 00:31:43,740
[PETER] Yeah, that's definitely right.

506
00:31:45,200 --> 00:31:46,780
So I think, I think,

507
00:31:47,980 --> 00:31:51,280
looking back, what I did, one thing I've done.

508
00:31:52,220 --> 00:31:53,520
The number of times is,

509
00:31:56,640 --> 00:32:02,560
so effectively, having new organizational
ideas, and a lot of those I've

510
00:32:03,140 --> 00:32:07,980
adopted from looking around into other open
source free software type of projects, right?

511
00:32:08,920 --> 00:32:10,500
So some of the ideas about having

512
00:32:11,920 --> 00:32:16,340
like a packagers' mailing list, for example,
a way to communicate with packagers.

513
00:32:16,460 --> 00:32:20,760
I've adopted, sort of gotten the idea from
somewhere else and brought it into Postgres.

514
00:32:21,620 --> 00:32:26,260
Also, some of the ideas around what is now
the funds group that works with software

515
00:32:26,260 --> 00:32:29,000
in the public interest to manage
the money for the project.

516
00:32:29,920 --> 00:32:33,160
Is partially, I don't want to take
credit for all of this, right?

517
00:32:33,200 --> 00:32:37,360
But I know I was involved in the initial
discussions based on ideas I got from

518
00:32:37,380 --> 00:32:39,120
the Debian project where I was involved.

519
00:32:40,320 --> 00:32:41,300
And things like that.

520
00:32:42,400 --> 00:32:47,660
So that I do like to look
around into other projects.

521
00:32:49,460 --> 00:32:50,560
And see what kind of

522
00:32:51,880 --> 00:32:55,200
organizational challenges and solutions
they have, and then bring some of them over.

523
00:32:56,048 --> 00:32:59,508
[CLAIRE] Well, and I'm glad you do, and I'm
glad other people on the project do, because

524
00:32:59,588 --> 00:33:04,508
obviously you don't want to start everything
from a blank sheet of paper. It's good to

525
00:33:05,588 --> 00:33:08,308
build on top of the shoulders
of people on other projects

526
00:33:09,368 --> 00:33:11,308
as it fits the needs of Postgres.

527
00:33:11,988 --> 00:33:16,008
Okay, so you were talking about different ways
that you contribute to the project, and obviously

528
00:33:16,048 --> 00:33:20,328
talked about how you contribute
as a developer in the code itself,

529
00:33:20,908 --> 00:33:24,308
how you spend cycles explaining things.

530
00:33:25,688 --> 00:33:28,088
And I don't know if when you
said that you were thinking of

531
00:33:28,908 --> 00:33:32,388
emails to the mailing list, right?
Because that's a form of explanation.

532
00:33:32,448 --> 00:33:35,748
Or if you were thinking of conference talks
or blog posts or whatever, and maybe you

533
00:33:35,788 --> 00:33:38,788
should tell us that. And then the third
thing you talked about was core team.

534
00:33:39,828 --> 00:33:44,728
You serve on that, and you have for
years, quite a while, I think, right?

535
00:33:46,448 --> 00:33:47,348
I don't even know how long.

536
00:33:47,780 --> 00:33:49,120
[PETER] Yes, I couldn't
actually tell you how long.

537
00:33:49,928 --> 00:33:51,148
[CLAIRE] Okay, neither one of us knows then.

538
00:33:52,028 --> 00:33:55,348
So those are three ways in which you
contribute, but I know there's more.

539
00:33:55,428 --> 00:33:57,468
So keep going with this enumerated.

540
00:33:56,780 --> 00:33:58,980
[PETER] Is there more? What else
is there more? Give me a hint.

541
00:33:59,388 --> 00:33:59,788
[CLAIRE] Oh, okay.

542
00:33:59,868 --> 00:34:03,488
Well, what about the SQL standard, and what
about the PGCA board, and what about...

543
00:34:03,600 --> 00:34:05,700
[PETER] Oh yes, yes, of course.

544
00:34:05,448 --> 00:34:10,088
[CLAIRE] And if you weren't thinking of conference
talks, then we should talk about that as well.

545
00:34:11,240 --> 00:34:12,680
[PETER] So let's talk about the...

546
00:34:11,848 --> 00:34:15,948
[CLAIRE] Mentoring? What about mentoring? That's
probably another way. I mean, so yeah, you got a lot.

547
00:34:15,840 --> 00:34:17,920
[PETER] Yeah, there's a lot
of things going on, right?

548
00:34:18,000 --> 00:34:21,240
Some of those, sometimes some of those
fade in and out as things go, but I

549
00:34:21,280 --> 00:34:22,820
guess they're all sort of active.

550
00:34:23,540 --> 00:34:27,920
So I, yeah, let's talk about the
PGCA. Postgres Community Association

551
00:34:28,980 --> 00:34:32,060
is a nonprofit organization
that was incorporated to manage,

552
00:34:33,020 --> 00:34:37,880
initially manage domain names for the
project, because someone has to have them.

553
00:34:39,420 --> 00:34:42,520
So it was more of a very low-key
organization, and then it

554
00:34:43,380 --> 00:34:46,180
turned out that we also needed to
guard the project's trademarks.

555
00:34:47,180 --> 00:34:50,780
And into other intellectual properties,
that has become a much, much bigger

556
00:34:51,680 --> 00:34:54,400
undertaking, so that takes up quite a bit of work.

557
00:34:55,840 --> 00:34:56,940
Amongst several people, right?

558
00:34:56,980 --> 00:34:59,680
It's not only me doing it, and of
course, Claire, you're doing it as well.

559
00:35:03,008 --> 00:35:06,488
[CLAIRE] And you served on that
board for quite a long time as well.

560
00:35:07,360 --> 00:35:09,280
[PETER] Yeah, that sort of also, yeah, that

561
00:35:10,520 --> 00:35:14,280
organization was initially chartered by
the core team, so I ended up in there also,

562
00:35:15,540 --> 00:35:17,680
in some way delegated by the core team originally.

563
00:35:19,040 --> 00:35:21,300
So yeah, that's also been going for a long time.

564
00:35:21,340 --> 00:35:25,860
Again, initially it was actually not
quite as much sort of work as it is now.

565
00:35:27,640 --> 00:35:29,300
So yeah, that's quite

566
00:35:30,040 --> 00:35:32,040
intense at times, as you know.

567
00:35:35,368 --> 00:35:39,048
[CLAIRE] And I'm still the, I'm still
the new kid on the block dealing with

568
00:35:35,600 --> 00:35:36,320
[PETER] What else did we talk?

569
00:35:39,588 --> 00:35:44,528
[CLAIRE] the PGCA board and all the responsibilities
of protecting the trademark. And it's

570
00:35:45,188 --> 00:35:51,628
interesting because some people equate open source
with open trademark, and it's not like that at

571
00:35:51,708 --> 00:35:55,248
all, right? Somebody does
have to protect it. So anyway.

572
00:35:56,388 --> 00:35:57,548
I don't want to dive into it.

573
00:35:56,920 --> 00:36:00,620
[PETER] Yeah, I mean, I wish it were different,
right? I wish there were some kind of

574
00:36:03,920 --> 00:36:07,680
free software, open source
was sort of born out of a

575
00:36:09,160 --> 00:36:11,800
hack of copyright law in a way, right? That

576
00:36:12,720 --> 00:36:16,080
you have to have copyrights, but you
write a license in a way that it's sort

577
00:36:16,120 --> 00:36:22,120
of mostly free for everyone, right? But such
a thing doesn't really exist in trademark law.

578
00:36:22,340 --> 00:36:28,500
I think that would actually be quite helpful,
but that's a totally much different discussion.

579
00:36:28,660 --> 00:36:29,880
I don't think we're going to solve that.

580
00:36:29,308 --> 00:36:34,508
[CLAIRE] It's a whole separate series of episodes
unto itself. So yeah, let's not go there.

581
00:36:34,928 --> 00:36:37,048
But I do, I do thank you for serving on that.

582
00:36:37,128 --> 00:36:40,488
I'm the new kid on the block, and I'm
still learning so much from the rest

583
00:36:40,528 --> 00:36:44,848
of you. But there's a lot.
What about the SQL standard?

584
00:36:44,988 --> 00:36:46,828
That's something that I think you work on.

585
00:36:46,928 --> 00:36:50,348
I think Vik Fearing works on
that as well. Am I right on that?

586
00:36:51,100 --> 00:36:56,760
[PETER] Yeah, that's actually, it's quite interesting.
I think for, obviously, Postgres implements SQL

587
00:36:57,820 --> 00:37:01,600
ever since, obviously there was a change
from what was it before, PostQUEL, right?

588
00:37:01,660 --> 00:37:04,040
But ever since I was involved, it's been SQL.

589
00:37:05,320 --> 00:37:09,060
And, but it was for forever, it
was just SQL was just a thing that

590
00:37:09,660 --> 00:37:11,800
sort of came out of somewhere, and we had no

591
00:37:12,380 --> 00:37:14,260
involvement in or knowledge of it at all.

592
00:37:14,320 --> 00:37:17,460
It's just sort of by rumor, it's
sort of a new version popped up,

593
00:37:18,060 --> 00:37:19,700
because the process is obscure, right?

594
00:37:21,320 --> 00:37:21,740
And,

595
00:37:24,200 --> 00:37:27,520
you know, initially there was
no way of even knowing how to

596
00:37:28,680 --> 00:37:29,400
do anything about it.

597
00:37:30,840 --> 00:37:32,300
But then over time, as you know, the

598
00:37:33,040 --> 00:37:35,640
project grew and the,

599
00:37:36,580 --> 00:37:39,160
you know, commercial opportunities,

600
00:37:40,200 --> 00:37:46,140
meaning, you know, availability of time
and money to do this kind of thing grew.

601
00:37:46,980 --> 00:37:51,420
Then it was possible to figure out, okay,
so where does this come from and who

602
00:37:53,760 --> 00:37:55,620
do we need to know to get involved in this, right?

603
00:37:55,660 --> 00:37:57,600
And so I was encouraged by

604
00:37:59,240 --> 00:38:03,120
my manager at the time, Simon Riggs,
to figure out how that should work.

605
00:38:03,160 --> 00:38:05,240
And I also happened... there was some

606
00:38:05,700 --> 00:38:09,000
fortunate circumstances there that I also
happened to be at an event where I met

607
00:38:09,680 --> 00:38:11,700
people who were already involved in that, and I...

608
00:38:12,660 --> 00:38:13,720
you know, just asked them, like, hey.

609
00:38:14,560 --> 00:38:17,740
I'm actually supposed to
find you. I just found you.

610
00:38:19,100 --> 00:38:24,400
And then, yeah, I got involved in
that, and it was, yeah, this is

611
00:38:24,900 --> 00:38:28,520
going five, six years now I've been
there, and we've been getting...

612
00:38:29,500 --> 00:38:31,760
even more community members
involved there now, right?

613
00:38:31,800 --> 00:38:35,140
You mentioned Vik, he's been around for
a couple of years now, and also I think

614
00:38:35,220 --> 00:38:36,900
as of recently, a couple more people.

615
00:38:38,280 --> 00:38:39,940
So we're growing the Postgres presence there.

616
00:38:41,020 --> 00:38:44,440
It's quite an interesting
group there as well because

617
00:38:45,300 --> 00:38:49,480
me coming from this open source way
of working where you have, you know,

618
00:38:50,500 --> 00:38:52,760
sort of a group of volunteers who have.

619
00:38:53,560 --> 00:38:56,200
You know, different commercial
interests perhaps, but common goals.

620
00:38:57,220 --> 00:38:58,640
It's quite easy for me to work there.

621
00:38:59,300 --> 00:39:01,602
Maybe it's unusual if you just come
from a company, you need to go to,

622
00:39:03,160 --> 00:39:04,800
you know, talk with other
companies about what to do.

623
00:39:04,840 --> 00:39:08,680
But for me, this was actually
quite easy, and it's super fun to

624
00:39:09,680 --> 00:39:14,540
just hang out with database nerds, some of
whom have been around for, we're talking for

625
00:39:14,580 --> 00:39:15,020
me here.

626
00:39:15,800 --> 00:39:18,660
What, 25 years? That's nothing
compared to some people who are there.

627
00:39:20,780 --> 00:39:24,620
So the body of knowledge that's
available there is immense.

628
00:39:23,838 --> 00:39:29,159
[CLAIRE] I know the name of the working
group is a really, really long name that I

629
00:39:29,638 --> 00:39:32,578
can't seem to commit to memory. But I'm curious

630
00:39:33,378 --> 00:39:39,878
how often do you all meet and do you
tend to meet virtually, like over

631
00:39:40,818 --> 00:39:45,078
Teams or Zoom or something like that?
Or are there in-person meetings as well?

632
00:39:45,938 --> 00:39:47,878
Where does the sausage get made?

633
00:39:49,160 --> 00:39:55,680
[PETER] So the group has, so the normal
cadence is there's about three meetings a year.

634
00:39:56,800 --> 00:39:59,760
These are in-person meetings, but
you can also dial in via Zoom.

635
00:40:01,400 --> 00:40:07,080
And again, in a way, there was some
fortunate timing there because,

636
00:40:07,140 --> 00:40:10,640
I guess don't know exactly how it was
before I joined, but I joined just around

637
00:40:10,680 --> 00:40:11,420
the time of COVID,

638
00:40:12,140 --> 00:40:15,460
where the in-person meetings
were obviously canceled and

639
00:40:16,680 --> 00:40:20,140
they had to kind of make up on the
spot, like most other people at the

640
00:40:20,200 --> 00:40:22,800
time, some way of continuing the work virtually.

641
00:40:23,000 --> 00:40:25,760
So there were a lot of virtual
meetings at the time over Zoom.

642
00:40:26,920 --> 00:40:27,560
And so the

643
00:40:29,400 --> 00:40:35,740
facility to actually have online meetings, virtual
meetings, was formalized at ISO at the time.

644
00:40:36,600 --> 00:40:37,760
So now it's pretty normal.

645
00:40:39,060 --> 00:40:41,019
Before that, it would have involved.

646
00:40:42,259 --> 00:40:46,000
You know, a lot of travel, effectively,
and at the time I joined, I could have

647
00:40:46,100 --> 00:40:47,300
just joined.

648
00:40:47,960 --> 00:40:51,320
You know, just joined Zoom meetings. I
had my work Zoom meetings and I had the

649
00:40:52,100 --> 00:40:54,340
other Zoom meetings, so it wasn't
really much of a difference. But

650
00:40:55,040 --> 00:40:56,700
that kind of turned out well.

651
00:40:57,400 --> 00:41:00,280
And so now it's a mix. There's
these three in-person meetings.

652
00:41:00,320 --> 00:41:03,200
Sometimes there's intermediate
meetings that are purely virtual, but

653
00:41:04,160 --> 00:41:07,280
I don't go to all of the
meetings in person. I dial into

654
00:41:07,760 --> 00:41:08,520
some of them also

655
00:41:09,280 --> 00:41:09,760
virtually.

656
00:41:10,038 --> 00:41:11,258
[CLAIRE] How big is the working group?

657
00:41:11,918 --> 00:41:12,598
Approximately.

658
00:41:14,580 --> 00:41:15,500
[PETER] It's not super big.

659
00:41:15,540 --> 00:41:20,040
It's between 10 and 20 people, so depending
on it fluctuates a little bit, but it's

660
00:41:20,100 --> 00:41:20,880
about like that, yeah.

661
00:41:22,858 --> 00:41:29,338
[CLAIRE] All right, so the SQL standards working group,
that's my colloquial name, not the official name.

662
00:41:30,100 --> 00:41:30,800
[PETER] That's good enough, yeah.

663
00:41:31,398 --> 00:41:35,398
[CLAIRE] In addition to developer, in addition to
explainer, in addition to core team, in addition to

664
00:41:35,418 --> 00:41:40,218
PGCA, what else? Other ways you
contribute. I mentioned mentorship.

665
00:41:42,818 --> 00:41:47,358
Floor Drees on the chat has
asked that I make sure to

666
00:41:47,838 --> 00:41:53,418
ask you about CRA as well, which does not
stand for Canadian Revenue Agency in this

667
00:41:53,458 --> 00:41:53,998
context.

668
00:41:55,378 --> 00:41:59,378
So let's tackle mentorship and CRA and
then see what else you could come up with.

669
00:42:01,160 --> 00:42:08,000
[PETER] Yeah, the mentorship is something I've
tried to participate in more. I got inspiration.

670
00:42:08,800 --> 00:42:12,060
And not just from that, from various
colleagues and community members.

671
00:42:12,440 --> 00:42:13,220
You know, some of you are,

672
00:42:13,625 --> 00:42:18,020
people will not be surprised, like
Robert Haas, for example, who has been

673
00:42:18,680 --> 00:42:20,380
pushing that for some time now.

674
00:42:21,200 --> 00:42:23,040
I do a lot of that

675
00:42:24,180 --> 00:42:28,320
internally in the company or just sort of
ad hoc with people, but I've also tried

676
00:42:28,340 --> 00:42:31,420
to participate in the community
mentorship programs that were organized.

677
00:42:33,320 --> 00:42:34,000
And yeah, that's.

678
00:42:33,378 --> 00:42:36,038
[CLAIRE] Yeah, shout out,
shout out to Robert on that.

679
00:42:36,560 --> 00:42:37,260
[PETER] Definitely, yeah.

680
00:42:38,218 --> 00:42:42,538
[CLAIRE] If any of you haven't listened to the
podcast episode we had with Robert where he

681
00:42:43,258 --> 00:42:45,978
talked a lot more and more deeply
about that mentorship program.

682
00:42:46,118 --> 00:42:48,398
You should listen, and I'll
include a link in the show notes.

683
00:42:49,100 --> 00:42:50,500
[PETER] Yeah, I think, and I think that's

684
00:42:52,460 --> 00:42:54,160
very, I mean, I enjoy that very much.

685
00:42:55,180 --> 00:42:57,540
But I think it was also needed a nudge from

686
00:42:58,460 --> 00:43:00,540
people like Robert and so on to actually,

687
00:43:01,560 --> 00:43:03,980
for me to realize that I
should do that now, right.

688
00:43:05,080 --> 00:43:08,380
It's sort of a responsibility
in a way to be available

689
00:43:09,700 --> 00:43:10,220
to people.

690
00:43:11,020 --> 00:43:11,820
And it's a way to

691
00:43:12,460 --> 00:43:16,380
grow the community and ultimately also
sustain my own job in a way, right?

692
00:43:18,720 --> 00:43:20,020
But that's good because you get to

693
00:43:20,660 --> 00:43:24,980
spend time with people who have different
backgrounds, and I hope to share knowledge, but also

694
00:43:25,040 --> 00:43:29,000
have actually learned a lot from
the people I was involved with.

695
00:43:30,088 --> 00:43:34,668
[CLAIRE] I mean, I think it's interesting that it's
probably harder to get started in Postgres today,

696
00:43:35,208 --> 00:43:39,888
even with all these programs, like the mentorship
program, than it was back when you started.

697
00:43:40,408 --> 00:43:44,528
Because back when you started, like you
said, it was very easy to find something that

698
00:43:44,588 --> 00:43:50,390
needed attention. You used the word
dubious, but, and there were fewer people.

699
00:43:53,108 --> 00:43:57,108
So it was easier to kind of get
into the circle, if you will. Now,

700
00:43:57,848 --> 00:44:01,988
I can see your face, which listeners can't,
and your brows are furrowed, so maybe you

701
00:44:02,028 --> 00:44:06,268
don't agree with me. Maybe it was equally
hard back then, but just differently hard.

702
00:44:06,808 --> 00:44:08,208
Maybe that's the comparison.

703
00:44:10,080 --> 00:44:11,900
[PETER] Well, I guess differently hard is

704
00:44:13,060 --> 00:44:14,360
probably true, right?

705
00:44:15,380 --> 00:44:20,440
It's, there was no process at the
time. It was just somehow it happened.

706
00:44:21,260 --> 00:44:24,620
You got tapped on the shoulder somehow,
so you wouldn't even know what to aim for,

707
00:44:24,700 --> 00:44:27,200
or you weren't even expecting it or aiming for it.

708
00:44:28,100 --> 00:44:30,960
Certainly nowadays people
have this, you know, certainly

709
00:44:31,560 --> 00:44:36,700
some people have an ambition to become a
contributor or a major contributor or committer or

710
00:44:36,720 --> 00:44:40,900
things like that, right? But back then
you didn't have these categorizations and

711
00:44:42,480 --> 00:44:46,360
these things were just assigned
to you in a way, right? So.

712
00:44:47,300 --> 00:44:49,780
It was hard in a way that you
didn't even know what to do. Now.

713
00:44:50,960 --> 00:44:54,580
I guess the expectations in the past are
hopefully a little bit more clear, but

714
00:44:55,380 --> 00:44:59,920
it's true, right? The standards
have risen, certainly the scrutiny,

715
00:45:00,820 --> 00:45:03,500
just the volume that is out of

716
00:45:04,060 --> 00:45:09,120
contributions and patches and emails and so
on has risen, so it's difficult to stand out,

717
00:45:09,620 --> 00:45:12,240
I assume, right? This is always difficult

718
00:45:12,740 --> 00:45:15,940
for me, and I assume others in a
similar position to actually know

719
00:45:17,080 --> 00:45:19,960
what the perception is, this is something
I learn like every day, like that.

720
00:45:20,660 --> 00:45:22,320
Other people don't have the same view of

721
00:45:24,180 --> 00:45:28,080
things as you do because they're not in the
same threads and the same discussions and

722
00:45:28,100 --> 00:45:30,080
the same Slack channels and the same meetings.

723
00:45:30,580 --> 00:45:33,700
So I don't know what the actual,
that's sort of always a...

724
00:45:36,060 --> 00:45:39,220
almost an unanswerable question from
my perspective. Is it easy? Is it hard?

725
00:45:39,300 --> 00:45:44,680
I hope to contribute to making it as easy
as sensible, but ultimately, I don't know.

726
00:45:45,588 --> 00:45:50,268
[CLAIRE] Well, and for anyone listening who is thinking
about getting involved in the Postgres project, just

727
00:45:50,348 --> 00:45:55,648
know that there are forums like
the Postgres Hackers Discord,

728
00:45:57,108 --> 00:46:00,028
where there are opportunities
to get mentored and to,

729
00:46:00,508 --> 00:46:06,608
and there are also committers who have regular
office hours that anybody can approach them to

730
00:46:07,208 --> 00:46:11,608
get a meeting and talk to them and ask
them questions one-on-one before they go on

731
00:46:11,648 --> 00:46:15,488
the mailing list and start
participating. So anyway,

732
00:46:16,068 --> 00:46:21,408
people are definitely taking steps like you
to try to make it easier to get involved.

733
00:46:21,928 --> 00:46:24,168
So I don't, I don't want to scare anyone away.

734
00:46:22,400 --> 00:46:27,340
[PETER] I would say personally,
no, I think trying to reach out.

735
00:46:28,893 --> 00:46:30,560
It's very sensible for people who,

736
00:46:32,200 --> 00:46:35,420
you know, are interested in pursuing
paths like that, right? Because,

737
00:46:36,720 --> 00:46:40,620
I mean, obviously the normal process would
just ideally be, you know, you send a lot

738
00:46:40,640 --> 00:46:43,420
of good patches and at some point
you get promoted to whatever

739
00:46:44,740 --> 00:46:45,880
kind of role.

740
00:46:46,620 --> 00:46:46,860
But,

741
00:46:47,980 --> 00:46:52,980
you know, to stand out or make connections
go into a conference if you can.

742
00:46:53,040 --> 00:46:56,480
That's not possible for
everybody, or go into meetups or

743
00:46:57,340 --> 00:47:01,280
going to online events such as hacking
workshops, patch review workshops,

744
00:47:02,360 --> 00:47:06,660
or anything like that where you
can present yourself as a person

745
00:47:07,400 --> 00:47:08,500
that people will remember

746
00:47:09,720 --> 00:47:10,760
is, I think, is valuable.

747
00:47:13,228 --> 00:47:16,988
[CLAIRE] I know we still need to get to the
CRA, but you just mentioned conferences.

748
00:47:17,868 --> 00:47:24,668
I know that's something that you participate
in on an annual basis, multiple times a year.

749
00:47:25,108 --> 00:47:28,148
I know that you were at PGDay
Lowlands. Was that last week?

750
00:47:30,688 --> 00:47:31,111
Which was in the Netherlands.

751
00:47:30,940 --> 00:47:32,400
[PETER] Yes, that was, yeah, actually, yeah.

752
00:47:32,548 --> 00:47:35,748
[CLAIRE] In the Netherlands, I think it
was the third annual event, and I think

753
00:47:37,828 --> 00:47:42,808
those organizers have coined the term that it's
the second best Postgres conference in Europe.

754
00:47:43,660 --> 00:47:46,660
[PETER] They do say that, yeah. I don't
know what the reference for that is.

755
00:47:46,780 --> 00:47:50,880
I mean, what the ranking is, what
the first and third one is, or

756
00:47:51,348 --> 00:47:52,948
[CLAIRE] I think they made up the ranking.

757
00:47:52,560 --> 00:47:55,240
[PETER] maybe sort of intentionally ambiguous.

758
00:47:55,748 --> 00:47:58,288
[CLAIRE] Intentionally ambiguous
is absolutely the right way.

759
00:47:57,360 --> 00:48:04,040
[PETER] No, but I will say, I will say that
Lowlands is the friendliest Postgres conference.

760
00:48:03,568 --> 00:48:04,648
[CLAIRE] Really? Okay.

761
00:48:04,120 --> 00:48:07,440
[PETER] I'm just gonna leave that out
there. Yeah, that's why I like coming back.

762
00:48:06,928 --> 00:48:10,948
[CLAIRE] I know they also have a fantastic
professional photographer each year,

763
00:48:11,428 --> 00:48:14,788
which means there are some great photos. Although,

764
00:48:15,468 --> 00:48:21,188
I'm just going to say that I was just looking
at the PGConf.dev LinkedIn account, where

765
00:48:21,748 --> 00:48:25,288
they posted photos of the
speakers from earlier this year.

766
00:48:25,368 --> 00:48:30,868
That's the annual event that usually takes place
in Canada that many of the contributors and

767
00:48:30,928 --> 00:48:35,508
committers attend. And there's
a lot of collaboration on

768
00:48:36,128 --> 00:48:38,748
the release that just happened,
the release that's coming up.

769
00:48:39,908 --> 00:48:43,188
And anyway, it's a super
wonderful conference as well.

770
00:48:42,210 --> 00:48:42,370
[PETER] Good.

771
00:48:43,828 --> 00:48:47,808
[CLAIRE] And I'm just going to say there are
some really nice photos of speakers on that

772
00:48:48,968 --> 00:48:51,468
conference as well. And they
did not hire a professional

773
00:48:51,488 --> 00:48:55,128
photographer, but they had some
nice volunteers. Wink, wink.

774
00:48:56,188 --> 00:48:56,628
Smile.

775
00:48:56,230 --> 00:48:57,350
[PETER] Yeah, I should check that out.

776
00:48:59,608 --> 00:49:02,068
[CLAIRE] Okay, so Lowlands is the
friendliest. You were just there.

777
00:49:02,148 --> 00:49:05,368
You gave a talk, and I know you're
also going to be giving a talk about

778
00:49:06,528 --> 00:49:12,608
CRA topic at PGConf.EU in
Valencia next month, in October.

779
00:49:14,312 --> 00:49:21,211
So PGConf.EU is probably the largest physical
in-person Postgres conference, happens every year,

780
00:49:21,472 --> 00:49:21,872
always,

781
00:49:22,672 --> 00:49:27,032
in a different, well, it rotates around
countries and cities of Europe. And

782
00:49:28,292 --> 00:49:31,112
when I say largest, it's, I don't
know, how many people is it going to be

783
00:49:31,152 --> 00:49:35,772
this year? 700, 800, something like that, I think.

784
00:49:35,390 --> 00:49:38,830
[PETER] Between six and eight is probably
the going rate at the moment, yeah.

785
00:49:39,712 --> 00:49:44,032
[CLAIRE] I think that the fact that it
rotates around different countries and cities

786
00:49:44,692 --> 00:49:50,152
is part of the secret sauce that makes
it so special. I know it's harder, right?

787
00:49:50,232 --> 00:49:52,892
Because you can't just exercise
the same playbook, right?

788
00:49:52,932 --> 00:49:56,092
The same hotel, the same relationships,
the same logistics every year.

789
00:49:58,990 --> 00:50:02,170
[PETER] It's interesting, yeah, because
some conferences, you mentioned PGConf.dev.

790
00:50:02,170 --> 00:50:04,670
PGConf.dev is sort of rotating now.

791
00:50:05,210 --> 00:50:07,730
We'll see how it goes in the long
run, but when it was in Ottawa.

792
00:50:09,090 --> 00:50:12,890
It was the same playbook for me every
year, and also at FOSDEM I mentioned in

793
00:50:12,910 --> 00:50:18,330
Brussels, it's sort of the same playbook every
year. And in some way that's also comfortable.

794
00:50:19,472 --> 00:50:22,472
[CLAIRE] Oh, cause you know exactly where
to stay and where to eat and you have your

795
00:50:19,670 --> 00:50:20,430
[PETER] But yeah.

796
00:50:22,532 --> 00:50:24,952
[CLAIRE] favorites and where the best beer is.

797
00:50:24,150 --> 00:50:24,850
[PETER] Exactly, right.

798
00:50:24,990 --> 00:50:27,330
Or you said like, Oh, I want to try
that one next time, or something like

799
00:50:27,390 --> 00:50:29,990
that. So that's also very
comfortable and reliable.

800
00:50:30,070 --> 00:50:34,330
But then also the ones that have, you know,
rotating locations, there's also sort of this

801
00:50:35,430 --> 00:50:38,470
mystery around it and stuff like that
every year, where would it be now and so

802
00:50:38,530 --> 00:50:39,870
on. So that's also fun, yeah.

803
00:50:42,012 --> 00:50:46,492
[CLAIRE] So you do make time to go to
conferences. Do you do it because it's fun

804
00:50:46,952 --> 00:50:50,612
or do you see that as a contribution
to the community as well? What's your,

805
00:50:51,172 --> 00:50:54,852
how do you justify the time you spend on
that, the time and the money, frankly.

806
00:50:56,170 --> 00:50:59,630
[PETER] Yeah, it's a combination of those
things, I think, right? Of course, it's fun.

807
00:51:02,830 --> 00:51:08,210
I think part of my job or role to be
present there and make myself available,

808
00:51:08,610 --> 00:51:13,370
or community members or commercial
partners, as the case may be,

809
00:51:15,210 --> 00:51:20,750
also giving presentations is a good way
of obviously promoting oneself, but also

810
00:51:21,910 --> 00:51:25,190
processing one's own thoughts into
a presentation is kind of almost.

811
00:51:26,430 --> 00:51:27,910
The most value out of that, you know,

812
00:51:29,670 --> 00:51:32,770
and learning things yourself as
you prepare for that kind of thing.

813
00:51:34,490 --> 00:51:35,870
But it's also, I think the

814
00:51:38,050 --> 00:51:42,090
human touch, the human contact
is important. I think this is,

815
00:51:43,310 --> 00:51:43,830
you know, I think

816
00:51:43,870 --> 00:51:45,890
we like

817
00:51:46,970 --> 00:51:50,010
working remotely online, most
people, this is the way it is.

818
00:51:50,290 --> 00:51:51,890
I mean, it's been in the Postgres community.

819
00:51:53,310 --> 00:51:55,350
Forever and also in many jobs now.

820
00:51:56,590 --> 00:51:59,750
But every once in a while, you have
to go and see that there are people

821
00:51:59,790 --> 00:52:02,650
on the other side and just have
a little fun together, and then

822
00:52:03,770 --> 00:52:09,770
that I think helps just the working environment
tremendously. So I think that's also necessary.

823
00:52:11,452 --> 00:52:14,112
[CLAIRE] Do you by any chance
remember where you first met me?

824
00:52:15,572 --> 00:52:16,812
I'm putting you on the spot.

825
00:52:17,570 --> 00:52:21,270
[PETER] I am going to say
that I was also at PGConf.EU

826
00:52:22,290 --> 00:52:22,670
in...

827
00:52:24,950 --> 00:52:25,510
where was that?

828
00:52:26,710 --> 00:52:27,710
Was it in Milan, maybe?

829
00:52:28,032 --> 00:52:28,412
[CLAIRE] Lisbon.

830
00:52:29,230 --> 00:52:31,250
[PETER] Lisbon, oh, even before
that. Okay, a year before that even.

831
00:52:31,512 --> 00:52:35,812
[CLAIRE] Yeah, so what was Lisbon? Is
that 2018, something like that? Yeah. So

832
00:52:37,232 --> 00:52:41,212
I was giving a talk about Postgres,
obviously, but it was like, why Postgres?

833
00:52:41,272 --> 00:52:45,892
Why this database? It was my perceptions
as someone new to the project on,

834
00:52:46,472 --> 00:52:47,032
you know, the...

835
00:52:47,832 --> 00:52:49,792
why it was so successful. And you even let me

836
00:52:51,172 --> 00:52:54,752
take a photo of you that was included
in the slides that were part of my

837
00:52:54,792 --> 00:52:55,032
talk.

838
00:52:55,930 --> 00:53:01,630
[PETER] I do remember that photo. That's
how I could frame the time frame, yeah.

839
00:52:59,112 --> 00:52:59,652
[CLAIRE] Place it.

840
00:53:02,492 --> 00:53:05,912
Okay, so conferences is a way that you contribute.

841
00:53:06,072 --> 00:53:12,372
And now let's dive into the talk that
you're going to be giving at PGConf.EU.

842
00:53:12,592 --> 00:53:15,892
And let me dig it up here. So it's the full title

843
00:53:16,412 --> 00:53:21,292
is, What does the EU Cyber Resilience
Act mean for Postgres and its community?

844
00:53:21,732 --> 00:53:29,631
And Cyber Resilience Act, that's what the CRA
acronym stands for, not Canadian Revenue Agency. So

845
00:53:30,251 --> 00:53:30,691
talk to me.

846
00:53:31,672 --> 00:53:35,332
What is that talk going to be about,
and why does CRA matter to us?

847
00:53:35,050 --> 00:53:40,290
[PETER] So I am actually quite
interested in also the politics

848
00:53:40,750 --> 00:53:43,430
and sort of the social role of open source.

849
00:53:44,090 --> 00:53:48,850
Maybe that's not something I'm visible
in, but I do follow that quite a bit.

850
00:53:50,070 --> 00:53:57,170
And so the Cyber Resilience Act is a
law that already exists and that will

851
00:53:57,670 --> 00:53:59,570
become active in the coming months.

852
00:54:02,970 --> 00:54:05,610
That regulates software, essentially, right? We

853
00:54:07,530 --> 00:54:08,070
have, you know,

854
00:54:08,930 --> 00:54:11,990
product regulation in many kinds of areas.

855
00:54:12,690 --> 00:54:14,690
Anything you buy has some kind of

856
00:54:15,510 --> 00:54:18,910
government regulation, whether you can buy it
in terms of safety and things like that. But

857
00:54:19,470 --> 00:54:22,950
software doesn't really, hasn't
really had that in general until now.

858
00:54:25,030 --> 00:54:30,230
But when that came, so when this
was first discussed some years ago,

859
00:54:31,330 --> 00:54:35,530
this you know, legislative initiative, there
was quite a bit of concern in the open source

860
00:54:35,570 --> 00:54:36,030
community

861
00:54:36,970 --> 00:54:40,370
about how that would impact open source work,

862
00:54:40,370 --> 00:54:45,930
because if you have a product category
that is regulated by some kind of

863
00:54:46,730 --> 00:54:47,750
government regulation, like

864
00:54:49,370 --> 00:54:52,850
how do you develop open
source that's in this sort of

865
00:54:54,070 --> 00:54:58,390
classic chaotic uncontrolled way, is that
still going to be possible and so on.

866
00:54:59,190 --> 00:55:01,870
So that was quite interesting
to me, and so I've...

867
00:55:02,810 --> 00:55:04,970
studied that quite a bit now and,

868
00:55:06,630 --> 00:55:10,790
yeah, and obviously I kind of mapped
that to my main work of how this

869
00:55:11,850 --> 00:55:15,390
would impact the work that I'm
doing, that we're doing in my

870
00:55:15,890 --> 00:55:17,230
job and in the community.

871
00:55:18,930 --> 00:55:20,050
But I think it's, you know,

872
00:55:21,750 --> 00:55:25,570
quite useful and actually has
quite good opportunities also, so.

873
00:55:26,450 --> 00:55:27,050
That's how I've

874
00:55:29,030 --> 00:55:30,210
got myself into that.

875
00:55:32,422 --> 00:55:35,722
[CLAIRE] Okay, well, and I think for those
of us who want to know more, we're going

876
00:55:35,722 --> 00:55:39,241
to have 45 minutes of an
opportunity. I assume it's a longer

877
00:55:40,462 --> 00:55:47,862
45-minute talk, is that right? Yeah.
So I will be there to find out more.

878
00:55:45,890 --> 00:55:46,230
[PETER] Oh, good.

879
00:55:50,302 --> 00:55:54,762
[CLAIRE] Are there other ways you contribute
to Postgres beyond what we talked about?

880
00:55:55,902 --> 00:56:01,662
Development, explaining things, core team,
PGCA, SQL standards, mentorship, conferences.

881
00:56:03,450 --> 00:56:05,530
[PETER] I don't know. How am
I supposed to do even more?

882
00:56:07,310 --> 00:56:11,130
I mean, also, I also have a job at
the alongside of all that, right?

883
00:56:11,430 --> 00:56:13,450
Yeah, so I also do,

884
00:56:15,170 --> 00:56:18,010
you know, without going into
too many details, I do a lot of

885
00:56:18,470 --> 00:56:23,630
that also, the parallels of that internally, you
know, for my colleagues and teams and products

886
00:56:23,670 --> 00:56:30,510
and things like that. So I'm also stretched
thin at times to satisfy all of those

887
00:56:31,290 --> 00:56:32,070
demands also.

888
00:56:34,022 --> 00:56:37,882
[CLAIRE] Right. And then of course,
you have, you have a family too,

889
00:56:34,530 --> 00:56:36,310
[PETER] There's not much time left.

890
00:56:38,562 --> 00:56:43,542
[CLAIRE] which needs time as well. So
that's a different type of contribution.

891
00:56:43,822 --> 00:56:48,302
And unless you have any budding Postgres
contributors that you're mentoring in your family,

892
00:56:49,062 --> 00:56:49,802
as in children.

893
00:56:50,770 --> 00:56:53,970
[PETER] No, it doesn't seem to be
turning that way at the moment, so.

894
00:56:56,022 --> 00:56:56,402
[CLAIRE] Got it.

895
00:56:58,062 --> 00:57:00,942
There was a blog you wrote in 2024

896
00:57:01,482 --> 00:57:03,382
that I wanted to give a shout out to.

897
00:57:03,442 --> 00:57:06,682
The title of it was, Where
are all the Postgres users?

898
00:57:08,022 --> 00:57:11,362
And you mentioned that way back in the beginning,

899
00:57:11,962 --> 00:57:14,662
earlier in the 25 years when you
first started with Postgres, it

900
00:57:15,162 --> 00:57:19,842
felt like there were a lot of users on the
mailing list because mailing list culture

901
00:57:20,622 --> 00:57:25,322
was a way that people communicated across
projects and in the open source world, even more

902
00:57:25,362 --> 00:57:28,142
so than today. So I'm really
curious, where are all the

903
00:57:28,822 --> 00:57:31,742
Postgres users, and can you
share with us a little bit of

904
00:57:32,322 --> 00:57:34,061
your thinking in writing that blog?

905
00:57:36,190 --> 00:57:40,990
[PETER] Yeah, exactly, right. This
came out of this realization that

906
00:57:42,170 --> 00:57:44,330
you had this notional

907
00:57:44,970 --> 00:57:49,290
development cycle in open source where you get
sort of this immediate feedback from users, and

908
00:57:49,330 --> 00:57:49,411
the hackers

909
00:57:52,950 --> 00:57:57,030
were all in the same shared space where
they could exchange information and

910
00:57:57,550 --> 00:57:59,830
get feedback immediately. And as

911
00:58:00,510 --> 00:58:04,030
over time, as things grow, as things
have grown and got more complex.

912
00:58:05,090 --> 00:58:05,270
That

913
00:58:06,410 --> 00:58:08,670
is not really happening that way anymore. I mean,

914
00:58:09,450 --> 00:58:14,390
it still appears, of course, there's still user
mailing lists, you know, where that kind of

915
00:58:15,010 --> 00:58:16,410
is happening, but it doesn't represent

916
00:58:17,230 --> 00:58:22,050
nearly the entire user base, and
I think most of the user base is

917
00:58:23,010 --> 00:58:26,630
silent in that way, right? They just
use Postgres and they have no need to

918
00:58:27,810 --> 00:58:31,450
contact the developers, or don't want to,
don't even know that they're there, right?

919
00:58:31,570 --> 00:58:35,270
Which is fine, right? I also use products
and don't want to talk to the manufacturer.

920
00:58:37,030 --> 00:58:40,410
But then you break this feedback loop.

921
00:58:41,830 --> 00:58:43,330
And I think a lot of the

922
00:58:45,990 --> 00:58:49,090
work that we, you know, we just discussed is

923
00:58:50,990 --> 00:58:54,630
finding that again, I'd go into
conferences and talking to random.

924
00:58:55,570 --> 00:58:56,090
So people.

925
00:58:57,130 --> 00:58:58,670
And hearing what they're

926
00:58:59,450 --> 00:59:03,130
using Postgres for, and you learn just
random things that you didn't know.

927
00:59:04,450 --> 00:59:04,790
And

928
00:59:05,890 --> 00:59:09,570
you know, writing blog posts in a way,
there's always, you could also do this sort

929
00:59:09,609 --> 00:59:11,190
of, you write blog posts that are sort of

930
00:59:11,930 --> 00:59:14,830
not partially wrong, but sort
of leave open questions and

931
00:59:15,430 --> 00:59:18,850
try to get feedback that way,
you know, that kind of thing, or,

932
00:59:21,630 --> 00:59:24,790
yeah, or just going into
these, you know, random...

933
00:59:26,350 --> 00:59:26,990
channels,

934
00:59:28,750 --> 00:59:30,750
events, you know, mentorship

935
00:59:31,890 --> 00:59:34,110
setups, user group meetings, and

936
00:59:34,890 --> 00:59:36,610
get the feedback that way, but it's difficult.

937
00:59:37,370 --> 00:59:39,630
But so it's not going to be like that anymore.

938
00:59:40,730 --> 00:59:42,350
But I think it is

939
00:59:44,830 --> 00:59:45,310
useful

940
00:59:46,390 --> 00:59:47,010
to keep that

941
00:59:49,330 --> 00:59:52,550
channel sort of up or have
that user feedback, right?

942
00:59:52,570 --> 00:59:53,770
Because obviously you want to make good product.

943
00:59:54,862 --> 00:59:58,482
[CLAIRE] I almost wonder if there needs
to be some marketing around it, right?

944
00:59:58,702 --> 01:00:05,622
Like some new initiative around a voice of
the Postgres customer coming into the Postgres

945
01:00:06,762 --> 01:00:07,322
community.

946
01:00:08,082 --> 01:00:11,282
I mean, so many customers use
Postgres in the cloud these days,

947
01:00:11,862 --> 01:00:16,702
or through a commercial offering,
and they're giving feedback, but to

948
01:00:17,162 --> 01:00:19,542
whoever the company is that they're paying, right?

949
01:00:21,062 --> 01:00:24,442
So if you work at EDB, you're
hearing from EDB customers. But

950
01:00:25,682 --> 01:00:30,642
if you're running on Azure, right, or AWS or
something, maybe that feedback is going to

951
01:00:30,682 --> 01:00:33,902
whoever your account managers are or
whoever your support team is there.

952
01:00:34,522 --> 01:00:36,742
And then it doesn't always trickle through to

953
01:00:38,362 --> 01:00:39,162
the contributors.

954
01:00:38,830 --> 01:00:42,730
[PETER] Yeah, so maybe this is a shout-out
to everyone. Just feedback is welcome, right?

955
01:00:43,202 --> 01:00:43,382
[CLAIRE] Yeah.

956
01:00:44,010 --> 01:00:46,710
[PETER] So, and obviously it
has to be aggregated ultimately.

957
01:00:47,410 --> 01:00:51,330
You can't have this sort of direct
relationship with everybody anymore.

958
01:00:53,382 --> 01:00:56,522
But it is super useful to just learn about

959
01:00:57,182 --> 01:01:00,522
how people use the products
and what their thoughts are.

960
01:01:01,982 --> 01:01:06,522
[CLAIRE] So there is another type of contribution
that I suspect you're making, which is

961
01:01:07,862 --> 01:01:11,282
each year there are probably some really
tough decisions that committers make.

962
01:01:11,382 --> 01:01:15,502
So we talked about you as a contributor,
contributing code, but you're also a committer.

963
01:01:16,162 --> 01:01:18,682
And as a committer, that means
you're reviewing a lot of patches,

964
01:01:19,182 --> 01:01:22,642
because anything that you commit,
you've implicitly reviewed, right?

965
01:01:23,122 --> 01:01:24,402
Otherwise you wouldn't be committing it.

966
01:01:24,242 --> 01:01:25,142
[PETER] Let's say that, sure.

967
01:01:26,462 --> 01:01:29,462
[CLAIRE] No, I know that's true. Come
on, are you telling me that's not true?

968
01:01:28,462 --> 01:01:30,722
[PETER] Yeah, yeah. No, no, it's true.

969
01:01:31,050 --> 01:01:31,270
[CLAIRE] Okay.

970
01:01:32,650 --> 01:01:37,850
So as a committer, which in other open source
projects the common term is maintainer, I

971
01:01:37,870 --> 01:01:42,910
would say, not exactly the same, but
the closest term. You review patches.

972
01:01:38,902 --> 01:01:39,472
[PETER] Sure, yeah.

973
01:01:43,150 --> 01:01:45,910
[CLAIRE] You work with people to
get things to the finish line,

974
01:01:46,430 --> 01:01:49,170
even if you're not a co-author
of whatever that patch is.

975
01:01:50,070 --> 01:01:56,110
There's a ton of work involved, but I also
suspect Postgres 19 is about to release

976
01:01:56,570 --> 01:01:57,910
beta 4, right?

977
01:01:58,070 --> 01:02:03,030
And presumably release candidate 1 sometime
in October, but beta 4 later in September.

978
01:02:03,130 --> 01:02:03,590
Is that right?

979
01:02:04,230 --> 01:02:08,470
And there's been a lot of decisions about
what stays in and what goes out. And

980
01:02:09,290 --> 01:02:13,790
I'm assuming you're involved in some of those
discussions and decisions, and that's another way you

981
01:02:13,810 --> 01:02:15,590
contribute, is in helping.

982
01:02:15,850 --> 01:02:18,190
Get each release to the finish line each year.

983
01:02:19,822 --> 01:02:23,902
[PETER] I do do that. I have to say
the hard work of deciding what needs to

984
01:02:24,362 --> 01:02:28,942
be removed is done by the release management
team that I am not participating in this

985
01:02:29,002 --> 01:02:29,202
year.

986
01:02:30,742 --> 01:02:31,702
There was

987
01:02:32,882 --> 01:02:36,662
three people. There's a release management
team every year of three people who are

988
01:02:37,222 --> 01:02:38,552
supposed to keep a really hard eye on
it, as opposed to just a normal eye

989
01:02:38,552 --> 01:02:38,602
on it.

990
01:02:42,930 --> 01:02:44,670
[CLAIRE] And you've done
that in previous releases.

991
01:02:44,582 --> 01:02:48,282
[PETER] I've done that also in
previous years, but it rotates around.

992
01:02:49,482 --> 01:02:51,602
But I think this year it's especially hard. I,

993
01:02:52,562 --> 01:02:55,002
which, I mean, the evidence is
there, right? There's been a lot of

994
01:02:55,982 --> 01:02:58,302
back and forth on various things, so.

995
01:03:01,542 --> 01:03:05,122
I'm not, I'm, I've been a
bit more on the receiving end

996
01:03:05,882 --> 01:03:07,902
this year than actually having
to make those decisions.

997
01:03:08,902 --> 01:03:12,482
But it is, yeah, I mean, just
getting the release ready is

998
01:03:14,082 --> 01:03:14,362
also

999
01:03:15,682 --> 01:03:18,002
something I contribute to
every year. This is sort of the

1000
01:03:19,082 --> 01:03:25,222
yearly cadence and, yeah, there's just a
lot of small things you want to do, just

1001
01:03:25,722 --> 01:03:27,122
tidy up things basically, right?

1002
01:03:28,162 --> 01:03:29,282
Make sure that things are polished.

1003
01:03:30,050 --> 01:03:32,090
[CLAIRE] Where do all these discussions about

1004
01:03:32,650 --> 01:03:36,070
what's staying in, is it
staying in, should it stay in,

1005
01:03:36,830 --> 01:03:39,810
where are all those discussions happening?
Is that on the hackers mailing list

1006
01:03:40,930 --> 01:03:43,370
or a separate release
management team mailing list?

1007
01:03:43,430 --> 01:03:47,030
If someone's listening and they're curious,
like, huh, I want to know more about this,

1008
01:03:48,010 --> 01:03:48,530
where do they go?

1009
01:03:50,842 --> 01:03:53,662
[PETER] In general, these things
should be on the hackers mailing list.

1010
01:03:55,422 --> 01:03:57,862
These discussions of this is,

1011
01:03:59,422 --> 01:04:01,682
this patch or this feature
doesn't seem to be quite ready.

1012
01:04:04,722 --> 01:04:07,742
But the release management team has its own.

1013
01:04:09,122 --> 01:04:11,762
I guess mailing list or email
alias or something like that,

1014
01:04:12,662 --> 01:04:14,322
where they discuss things and

1015
01:04:15,222 --> 01:04:18,762
what exactly goes on there? I
don't know this year, right? The...

1016
01:04:20,182 --> 01:04:22,982
since it's new people every year,
the style might also differ.

1017
01:04:23,062 --> 01:04:25,462
Maybe some people just have
occasional discussions.

1018
01:04:25,542 --> 01:04:28,382
I know some teams in the
past have had sort of weekly.

1019
01:04:29,962 --> 01:04:31,082
Meetings and things like that.

1020
01:04:31,922 --> 01:04:34,262
So there might be some like that. It is a bit,

1021
01:04:35,062 --> 01:04:38,862
right now, I think it's a bit confusing because

1022
01:04:39,562 --> 01:04:43,962
some of those discussions are also spread over
other private mailing lists for release management

1023
01:04:44,042 --> 01:04:48,382
and some private email threads where
people send additional feedback on things.

1024
01:04:48,402 --> 01:04:53,902
So it's a bit confusing, actually, perhaps,
right now. But generally, most of this should be

1025
01:04:54,382 --> 01:04:57,202
documented on the hackers mailing list. And

1026
01:04:57,962 --> 01:05:02,342
if not, if people, you know, listening
and trying to follow this, if it's not

1027
01:05:02,902 --> 01:05:06,462
publicly documented, they feel,
then please also ask for it.

1028
01:05:07,362 --> 01:05:08,501
It's a bit like what I said earlier.

1029
01:05:08,722 --> 01:05:11,821
It's not always very easy to see
what views other people have.

1030
01:05:12,222 --> 01:05:14,342
I see that a lot when I talk to people about some,

1031
01:05:16,202 --> 01:05:18,622
you know, question or misunderstanding
perhaps, or something like that.

1032
01:05:19,102 --> 01:05:21,082
Like, well, of course it's
like that, and they didn't

1033
01:05:21,822 --> 01:05:26,282
even know that because they were somehow not
involved in that thread or discussion or email,

1034
01:05:26,962 --> 01:05:27,162
you know.

1035
01:05:29,622 --> 01:05:31,102
If people feel they don't

1036
01:05:31,702 --> 01:05:35,482
really see what the process is in general,
in this case or in general, also please

1037
01:05:36,262 --> 01:05:37,902
point that out. That would also be useful.

1038
01:05:39,150 --> 01:05:43,650
[CLAIRE] I know there's a question on the
chat, someone who wants to hear the story

1039
01:05:44,450 --> 01:05:48,810
or hear some perspective on the
revert of SQL/PGQ for Postgres 19.

1040
01:05:50,209 --> 01:05:54,090
So I will say that, yeah, people probably
are curious, like what happened there?

1041
01:05:54,250 --> 01:05:55,010
What's the story?

1042
01:05:55,890 --> 01:05:58,650
I don't know that we want to dive into
it here because that's probably a whole

1043
01:05:58,710 --> 01:06:03,770
half-hour-long or hour-long
discussion in and of itself. So.

1044
01:06:05,010 --> 01:06:06,930
But it does, it does make me.

1045
01:06:07,770 --> 01:06:10,690
Want to shine a light on the work
you do as a Postgres committer,

1046
01:06:11,510 --> 01:06:14,710
because that is one of the ways
you contribute, right? If you

1047
01:06:15,270 --> 01:06:21,850
were a contributor who just does their own thing,
right, co-authors patches, that's one thing.

1048
01:06:21,950 --> 01:06:26,410
But you also are doing patch review and
helping other people get to the finish line

1049
01:06:26,630 --> 01:06:26,910
and

1050
01:06:28,530 --> 01:06:33,430
advising on who, I assume the
existing set of committers

1051
01:06:33,950 --> 01:06:37,130
have a process by which you decide who should be

1052
01:06:37,850 --> 01:06:41,070
invited to be a committer in the
future, right? So that's another

1053
01:06:41,590 --> 01:06:47,110
part of being a committer, is helping
grow that community, nurture, groom,

1054
01:06:48,130 --> 01:06:49,730
advise, mentor, all that stuff.

1055
01:06:50,430 --> 01:06:50,570
So

1056
01:06:51,630 --> 01:06:55,270
drumroll. What's it, what's it
like to contribute in that way?

1057
01:06:55,750 --> 01:06:57,250
How long have you been a committer?

1058
01:07:00,038 --> 01:07:03,538
[PETER] I think, again, we would have to
look it up, but it was quite early on,

1059
01:07:04,198 --> 01:07:05,718
might have been.

1060
01:07:08,078 --> 01:07:10,798
2000, 2001, something like that.

1061
01:07:12,318 --> 01:07:17,418
Because, again, the process was
not nearly as formalized back then.

1062
01:07:17,518 --> 01:07:22,478
So it was, I think the story was
told that if you annoyed Bruce

1063
01:07:23,398 --> 01:07:24,558
too much, then he would...

1064
01:07:25,198 --> 01:07:31,718
so Bruce Momjian was doing a lot of work
integrating other people's patches at the time,

1065
01:07:33,418 --> 01:07:34,098
and

1066
01:07:35,658 --> 01:07:38,558
if you sent him too many patches, then
he would just let you do it himself,

1067
01:07:39,018 --> 01:07:41,878
yourself. So that was sort of
the notional process, right?

1068
01:07:42,558 --> 01:07:45,518
If you gave him too much work, then he
would pass the work to you directly.

1069
01:07:49,538 --> 01:07:49,898
But yeah,

1070
01:07:52,058 --> 01:07:54,398
sometimes it's easy,

1071
01:07:55,318 --> 01:07:59,078
because you're just in the
flow and you do your things and

1072
01:07:59,698 --> 01:08:01,518
you produce nice things.

1073
01:08:02,218 --> 01:08:06,178
But sometimes it's difficult
and scary, right? Because you're

1074
01:08:07,118 --> 01:08:10,078
in a way, a little bit on your own.
Obviously, there's other people who

1075
01:08:10,558 --> 01:08:11,998
are available in theory to help, but

1076
01:08:12,878 --> 01:08:17,338
everybody's obviously super busy and
focused on their own project and so on.

1077
01:08:17,378 --> 01:08:18,158
And so when you then,

1078
01:08:19,958 --> 01:08:23,858
you know, you have a patch, either
something you wrote yourself or

1079
01:08:24,398 --> 01:08:26,398
from someone else that you plan to commit, and

1080
01:08:27,038 --> 01:08:28,778
at the end of the day, it's just

1081
01:08:30,058 --> 01:08:30,298
you

1082
01:08:31,678 --> 01:08:32,098
and,

1083
01:08:35,298 --> 01:08:37,398
you know, deciding to send that out,

1084
01:08:38,578 --> 01:08:43,538
and then it goes from you more or less
directly to everybody who uses it,

1085
01:08:44,358 --> 01:08:44,578
right?

1086
01:08:45,918 --> 01:08:46,478
And you're

1087
01:08:47,238 --> 01:08:50,218
tired and trying to get to dinner,
and then you just do it or not.

1088
01:08:50,398 --> 01:08:52,898
Or it's like that, right? So it is

1089
01:08:53,618 --> 01:08:56,098
sometimes a little scary if you
think about it too much. So maybe

1090
01:08:57,498 --> 01:09:00,279
you should do that once in a while, but

1091
01:09:00,318 --> 01:09:01,418
can also be a little bit.

1092
01:09:04,198 --> 01:09:05,278
Not productive to do that.

1093
01:09:05,260 --> 01:09:11,260
[CLAIRE] I know that Robert Haas
gave a talk at PGConf.dev in Canada.

1094
01:09:11,760 --> 01:09:14,900
I think it was last year, so
it would have been Montreal.

1095
01:09:14,318 --> 01:09:15,858
[PETER] Yeah, yeah, that was a good one, yeah.

1096
01:09:16,340 --> 01:09:19,140
[CLAIRE] And it was about, I
forget the exact name of the title.

1097
01:09:19,200 --> 01:09:22,720
I'll include it in the show
notes, but it was about being

1098
01:09:23,580 --> 01:09:24,860
a committer and what it's like.

1099
01:09:25,180 --> 01:09:28,580
And he had these fabulous
two diagrams, which he let me

1100
01:09:29,600 --> 01:09:34,080
use in a talk I gave later
at FOSDEM earlier this year.

1101
01:09:35,220 --> 01:09:40,760
And these diagrams showed what people, going
back to what you said earlier about how people

1102
01:09:40,800 --> 01:09:44,240
might view the same thing differently
and have a different perspective on it.

1103
01:09:44,600 --> 01:09:49,040
He had a diagram of a man who
looked like a king with a crown on

1104
01:09:49,079 --> 01:09:53,060
his head, sitting there with a big smile on
his face, you know, feeling accomplished.

1105
01:09:53,700 --> 01:09:55,780
And that was kind of like how he thought people

1106
01:09:56,780 --> 01:09:59,160
looked at committers when
they had just done a commit.

1107
01:09:59,440 --> 01:10:02,440
And then he showed another picture
of a very harried person with

1108
01:10:03,580 --> 01:10:07,920
hair coming out of their head at all
angles and tears on their face and sweating

1109
01:10:07,980 --> 01:10:13,340
and running, and this is what it actually
really feels like when you've just done a

1110
01:10:13,380 --> 01:10:15,120
commit. It's a little scary.

1111
01:10:14,778 --> 01:10:18,158
[PETER] Yeah, that's what I felt like
what I mentioned earlier when you commit.

1112
01:10:19,158 --> 01:10:20,378
You know, just before you go home.

1113
01:10:21,198 --> 01:10:24,918
And then an hour later, you see
that the buildfarm is on fire.

1114
01:10:26,458 --> 01:10:29,338
And then you learn your lessons
from that. But I think the,

1115
01:10:30,238 --> 01:10:34,538
you said the term maintainer, I think that's
maybe a better term nowadays, right? At the

1116
01:10:35,478 --> 01:10:40,958
beginning, as I mentioned, it was
almost more of a mechanical role that

1117
01:10:41,538 --> 01:10:44,538
instead of going through Bruce often.

1118
01:10:46,178 --> 01:10:48,398
You just do it yourself, but now.

1119
01:10:49,878 --> 01:10:53,418
I mean, I don't know how explicit this is,
but at least many people would understand

1120
01:10:53,438 --> 01:10:56,178
it that way, and I think that's reasonable
that you maintain or that you have not

1121
01:10:56,238 --> 01:10:56,958
only the role of,

1122
01:10:57,798 --> 01:10:59,218
you know, actually making the commits, but

1123
01:11:00,698 --> 01:11:03,178
being somehow having a role in the community to

1124
01:11:04,458 --> 01:11:07,478
work with others who are not committers maybe to

1125
01:11:08,558 --> 01:11:10,758
help move their things along and

1126
01:11:11,938 --> 01:11:13,838
ultimately mentor them to, again,

1127
01:11:15,018 --> 01:11:17,897
mentor them to be their own
committers, so maybe in some cases.

1128
01:11:19,918 --> 01:11:25,058
And also just have a responsibility for
the whole process, essentially, right?

1129
01:11:25,938 --> 01:11:30,938
It's a very fine-tuned process
nowadays with the commitfests and the

1130
01:11:31,838 --> 01:11:37,318
release candidates and betas and buildfarms and
all these things that we've built up over the

1131
01:11:37,358 --> 01:11:42,058
years that you have a shared
responsibility for and, if necessary, also.

1132
01:11:43,178 --> 01:11:45,578
You know, evolving and improving those things.

1133
01:11:46,898 --> 01:11:49,458
So I think that also comes with the role.

1134
01:11:51,020 --> 01:11:52,220
[CLAIRE] One of the things that

1135
01:11:53,580 --> 01:11:58,700
I really like about working with you, and
of course, we've only worked with each other

1136
01:11:58,800 --> 01:12:04,020
in narrow ways because so much of your
job does not involve me, unfortunately.

1137
01:12:06,100 --> 01:12:07,180
You're a very good listener.

1138
01:12:08,060 --> 01:12:12,900
And you give very thoughtful feedback.
I can tell you're processing it.

1139
01:12:13,000 --> 01:12:14,700
You're not jumping to conclusions. You're

1140
01:12:15,220 --> 01:12:19,320
looking at it from whatever the topic is,
from different angles and things like that.

1141
01:12:19,380 --> 01:12:22,320
So I personally love working with you.

1142
01:12:22,520 --> 01:12:27,080
And after walking through all the many different
ways that you contribute to this project,

1143
01:12:27,640 --> 01:12:31,260
I'm just going to say on behalf
of the rest of the world that I

1144
01:12:31,720 --> 01:12:33,420
thank you for

1145
01:12:34,400 --> 01:12:34,860
what you do.

1146
01:12:35,658 --> 01:12:36,358
[PETER] Well, thank you for that.

1147
01:12:37,038 --> 01:12:38,258
Thank you for that feedback. I...

1148
01:12:39,478 --> 01:12:40,298
yeah, that's good to know

1149
01:12:40,918 --> 01:12:43,678
if people think that, or if you at
least you think that's good to know.

1150
01:12:43,900 --> 01:12:46,820
[CLAIRE] I mean, I can remember
standing with you and in Riga,

1151
01:12:47,820 --> 01:12:52,140
in the hallway they had those tall cocktail
tables and I had my laptop open and

1152
01:12:52,180 --> 01:12:55,500
I was showing you a proposal I
had for something and you were,

1153
01:12:56,080 --> 01:12:56,900
you took the time.

1154
01:12:57,140 --> 01:13:00,660
You weren't harried, you weren't in a hurry,
you weren't half listening, you were, you were

1155
01:13:00,700 --> 01:13:01,800
really focused on it, so.

1156
01:13:02,820 --> 01:13:05,980
Okay, I'm going to ask you a different
question. It's what I call the toothbrush test.

1157
01:13:07,340 --> 01:13:10,820
So my husband introduced me to
this many, many, many years ago.

1158
01:13:11,500 --> 01:13:14,520
But the idea is when you're brushing your
teeth in the morning, which I hope you

1159
01:13:14,560 --> 01:13:17,440
do because it's good for
dental hygiene and all of that,

1160
01:13:18,148 --> 01:13:18,788
[PETER] Let's say that, yeah.

1161
01:13:18,580 --> 01:13:23,180
[CLAIRE] are you looking forward to
your work? Are you looking forward to

1162
01:13:24,460 --> 01:13:25,600
the things you're going to be doing?

1163
01:13:26,420 --> 01:13:30,900
And so as you think about all these different
ways in which you participate in Postgres

1164
01:13:30,920 --> 01:13:31,460
and contribute,

1165
01:13:32,440 --> 01:13:33,880
Does it pass the toothbrush test?

1166
01:13:34,888 --> 01:13:38,208
[PETER] So the toothbrush test is, as I'm
brushing my teeth in the morning, do I look

1167
01:13:38,328 --> 01:13:40,188
forward to the workday ahead?

1168
01:13:41,340 --> 01:13:46,440
[CLAIRE] Yeah, where I mean not just EDB, but
your Postgres open source community work as well.

1169
01:13:48,020 --> 01:13:49,480
Everything, all the Postgres work.

1170
01:13:48,408 --> 01:13:52,028
[PETER] Yeah, absolutely.
Yeah, yeah, absolutely. This is

1171
01:13:53,208 --> 01:13:56,288
from the time I wake up, probably
I have thoughts and plans,

1172
01:13:56,748 --> 01:14:01,748
or sometimes I can't even sleep because
that's just probably not a good sort of

1173
01:14:02,208 --> 01:14:05,048
sleep hygiene that you go to
bed with problems in your head,

1174
01:14:06,548 --> 01:14:11,088
or sort of tasks in your head, not
problems necessarily. So definitely, yeah.

1175
01:14:12,728 --> 01:14:13,687
As soon as the

1176
01:14:14,708 --> 01:14:19,508
toothbrushing is done and the kids are
out of the house for school, I'm ready to

1177
01:14:19,548 --> 01:14:19,708
go.

1178
01:14:19,950 --> 01:14:22,210
[CLAIRE] Well, that's.

1179
01:14:21,708 --> 01:14:26,488
[PETER] Especially because the mornings are free
of meetings usually, and sort of up until the

1180
01:14:26,948 --> 01:14:29,308
lunchtime there's free time.

1181
01:14:29,950 --> 01:14:33,370
[CLAIRE] And that's deliberate on your
part, like you block your calendar.

1182
01:14:32,088 --> 01:14:33,628
[PETER] That's just the way the timing worked.

1183
01:14:33,988 --> 01:14:38,208
That's just the way the timing worked
out because most of the meetings are

1184
01:14:38,848 --> 01:14:42,108
either with colleagues in
North America, let's say, or

1185
01:14:42,968 --> 01:14:46,028
team meetings that are scheduled in this sort of

1186
01:14:47,168 --> 01:14:54,148
precious two hours or so where Europe, North
America can meet comfortably. So that is,

1187
01:14:55,368 --> 01:14:58,248
from starting sort of 2 p.m.
my time, then there's...

1188
01:14:59,268 --> 01:15:00,628
2 p.m. to 6 p.m., there's.

1189
01:15:01,548 --> 01:15:07,568
So usually meetings scattered and not
really much big blocks of time. So

1190
01:15:08,068 --> 01:15:12,268
the mornings are the good sort
of creative if you want, or,

1191
01:15:13,608 --> 01:15:17,848
you know, time to get really into the
zone if you want, or things like that.

1192
01:15:17,908 --> 01:15:18,888
So yeah, that's definitely...

1193
01:15:19,948 --> 01:15:22,448
if it were the other way around, it
would probably be a little bit more

1194
01:15:19,950 --> 01:15:20,370
[CLAIRE] I'm actually.

1195
01:15:23,648 --> 01:15:25,928
[PETER] ambivalent about it. But
this way, it's actually quite nice.

1196
01:15:27,110 --> 01:15:31,610
[CLAIRE] I'm actually quite jealous of teammates and
colleagues who work in Europe because I know when

1197
01:15:31,690 --> 01:15:35,830
I'm there, let's say I go for a
conference, if I stay an extra day or

1198
01:15:35,890 --> 01:15:37,490
two and I work on the side,

1199
01:15:39,150 --> 01:15:40,310
I get so much done

1200
01:15:41,050 --> 01:15:45,250
in the morning until about four o'clock in
the afternoon when West Coast U.S. wakes up.

1201
01:15:45,768 --> 01:15:46,368
[PETER] There it is, yep.

1202
01:15:45,950 --> 01:15:50,470
[CLAIRE] And then it, then it all of a
sudden my brain gets into tactical mode. But

1203
01:15:50,930 --> 01:15:52,990
earlier in the day, yeah, you can be creative.

1204
01:15:53,450 --> 01:15:56,590
You can, you can think about things
that take a little bit longer.

1205
01:15:58,130 --> 01:15:59,549
I'm just, I just love it.

1206
01:16:00,269 --> 01:16:04,030
Whereas here, you wake up in California and
you're playing catch up from the moment you

1207
01:16:04,070 --> 01:16:04,450
wake up.

1208
01:16:04,690 --> 01:16:08,650
You know, there's already so much that's happened,
starting with Europe and the East Coast and

1209
01:16:09,550 --> 01:16:11,590
anyway, time zones, I guess.

1210
01:16:12,250 --> 01:16:16,090
All right, so if somebody is listening and
they want to get involved in Postgres as

1211
01:16:16,110 --> 01:16:16,650
a contributor.

1212
01:16:17,510 --> 01:16:19,110
What would your recommendation to them be?

1213
01:16:22,908 --> 01:16:26,928
[PETER] I think first of all, as you
have emphasized also, and there's

1214
01:16:27,488 --> 01:16:32,068
many different ways to contribute, right?
Obviously, you want to pick something that is

1215
01:16:32,648 --> 01:16:33,968
of interest to you if you're

1216
01:16:35,608 --> 01:16:38,708
you know, a user and you want to just
talk about your work, you can become

1217
01:16:38,748 --> 01:16:41,668
a speaker. If you're a developer,
obviously you want to do some development.

1218
01:16:43,768 --> 01:16:45,548
And various other things
we talked about, right? So.

1219
01:16:46,768 --> 01:16:48,088
It doesn't only have to be

1220
01:16:48,948 --> 01:16:50,108
writing code and patches.

1221
01:16:52,648 --> 01:16:56,828
In, I guess in most cases you just
do it, right? It sounds a little bit

1222
01:16:57,408 --> 01:16:58,128
simplistic, but

1223
01:16:59,128 --> 01:17:05,608
it doesn't, there's no, you don't need permission,
maybe from your boss or your spouse perhaps,

1224
01:17:06,908 --> 01:17:11,548
but you can submit a talk or you
can write a blog post or you can

1225
01:17:11,628 --> 01:17:16,008
send a patch or you can just discuss
things, you know, go to the mailing list

1226
01:17:16,068 --> 01:17:18,648
or Discord and contribute
to the discussions there.

1227
01:17:19,190 --> 01:17:23,370
[CLAIRE] Go to a local meetup. There are so many
amazing Postgres user groups around the globe.

1228
01:17:25,687 --> 01:17:26,388
[PETER] Yeah, definitely.

1229
01:17:26,468 --> 01:17:30,668
I think that's a good way to sometimes
you'll meet me there or you meet some

1230
01:17:30,747 --> 01:17:35,068
other senior developer there. Maybe
that's a good contact you can make.

1231
01:17:36,088 --> 01:17:37,968
Or just meet fellow users, so.

1232
01:17:39,868 --> 01:17:41,268
In a way, you know,

1233
01:17:43,728 --> 01:17:47,028
I think it should start with a
genuine interest, right? If you just

1234
01:17:47,668 --> 01:17:51,588
need to do it because you feel like it's
for career development or your boss told

1235
01:17:51,628 --> 01:17:54,848
you to do it or something like that, sure,
you can do that too. It's legitimate.

1236
01:17:54,908 --> 01:17:56,988
But if you want to do it

1237
01:17:58,528 --> 01:17:59,828
so long term somehow.

1238
01:18:00,728 --> 01:18:04,048
Then I think it should start with a genuine
interest that you're interested in the community,

1239
01:18:04,088 --> 01:18:08,648
the technology, or some aspect like that. And
then, because then you stick around naturally.

1240
01:18:09,488 --> 01:18:10,048
If, you know,

1241
01:18:11,368 --> 01:18:14,488
if it turns out you have a
knack for it and some talent and

1242
01:18:15,308 --> 01:18:18,388
you get along with the people who are
already there, then it becomes easy.

1243
01:18:18,768 --> 01:18:20,788
And you just stick around naturally.

1244
01:18:21,490 --> 01:18:24,990
[CLAIRE] Are you the person who once said,
come for the code, stay for the community?

1245
01:18:25,550 --> 01:18:26,030
Was that you?

1246
01:18:26,788 --> 01:18:28,148
[PETER] No, but that's good.

1247
01:18:29,668 --> 01:18:31,408
That's true in a way, right?

1248
01:18:29,790 --> 01:18:34,370
[CLAIRE] A lot of people do come for the
open source aspect, right, or the open source

1249
01:18:34,470 --> 01:18:39,610
project aspect, whether it's the code or
just other aspects of a community. But yeah,

1250
01:18:40,450 --> 01:18:43,210
once you meet the people, once
you start working with them,

1251
01:18:43,670 --> 01:18:46,370
once you see all the different
things that need doing

1252
01:18:46,910 --> 01:18:51,410
that you are good at, I don't know. A
lot of people stay for the community.

1253
01:18:49,648 --> 01:18:52,928
[PETER] Yeah, I think you come for the
code or the, you come for the code or

1254
01:18:52,988 --> 01:18:54,188
some other task, right?

1255
01:18:54,928 --> 01:19:00,208
That you're a conference speaker or something
like that, and then you stick around because you

1256
01:19:00,248 --> 01:19:04,208
like the event or the community, and you
come back the following years and things like

1257
01:19:04,248 --> 01:19:08,088
that. So I think, again, it should
start, I think, from an interest, right?

1258
01:19:08,168 --> 01:19:09,888
You don't come just for the community.

1259
01:19:10,772 --> 01:19:14,812
That is probably not going to be sustainable
because you don't have anything to do there,

1260
01:19:14,892 --> 01:19:18,352
just hanging out is maybe also okay, but
it's not really sustainable. So I think

1261
01:19:20,092 --> 01:19:22,832
that's a good, a good slogan, so to speak.

1262
01:19:24,070 --> 01:19:26,190
[CLAIRE] Okay, now I'm going to put
you on the spot before we wrap up.

1263
01:19:26,590 --> 01:19:29,910
What are your favorite
Postgres conferences and why?

1264
01:19:34,310 --> 01:19:38,410
You can give conferences with an
S. You don't have to give just one.

1265
01:19:40,432 --> 01:19:42,012
[PETER] I think I'm gonna say FOSDEM.

1266
01:19:43,450 --> 01:19:43,930
[CLAIRE] Really?

1267
01:19:44,532 --> 01:19:44,892
[PETER] Yeah.

1268
01:19:45,430 --> 01:19:49,210
[CLAIRE] Do you mean FOSDEM, or do you mean
FOSDEM PGDay, or do you mean the combination

1269
01:19:45,792 --> 01:19:46,032
[PETER] And,

1270
01:19:49,250 --> 01:19:51,090
[CLAIRE] of FOSDEM and FOSDEM PGDay?

1271
01:19:50,192 --> 01:19:52,732
[PETER] I think the combin-
I think the combination.

1272
01:19:53,892 --> 01:19:57,292
And because of the combination, right? Because it,

1273
01:19:57,772 --> 01:19:59,212
well, first of all, it's a bit sort of

1274
01:19:59,892 --> 01:20:03,692
close to my heart because it was my
first event and things like that. But

1275
01:20:04,432 --> 01:20:07,412
the useful thing there is you have Postgres

1276
01:20:08,352 --> 01:20:10,692
content and you get to meet the

1277
01:20:11,672 --> 01:20:16,452
Postgres community members, and sort of it's a
yearly, nowadays it's sort of a yearly gathering

1278
01:20:16,492 --> 01:20:17,392
and sort of has sort of a

1279
01:20:17,852 --> 01:20:22,072
tactical component to it too because it's
sort of close to feature freeze and so on.

1280
01:20:22,112 --> 01:20:25,012
So that's useful, but also because
you can go to all the other things,

1281
01:20:25,792 --> 01:20:26,772
you can go to

1282
01:20:28,892 --> 01:20:30,672
you know, sometimes just go to a random.

1283
01:20:31,732 --> 01:20:35,712
Room for another project, and just
it's what I mentioned earlier, right?

1284
01:20:35,772 --> 01:20:39,612
You learn from them not necessarily what their
coding standards are or something, but maybe that's

1285
01:20:39,652 --> 01:20:43,432
also useful actually, but just what
challenges they have in their communities,

1286
01:20:44,632 --> 01:20:46,492
what they're working on, or maybe what

1287
01:20:47,112 --> 01:20:52,132
issues they have with tooling or policies
or things like that, or you just learn other

1288
01:20:52,232 --> 01:20:54,412
stuff. And the combination of that, I think, is

1289
01:20:55,712 --> 01:20:58,892
what was, I always, it sort
of stands out that way.

1290
01:20:58,240 --> 01:21:03,560
[CLAIRE] Yeah, but to really benefit from
FOSDEM, I think you've got to work at it.

1291
01:21:04,599 --> 01:21:06,180
And what I mean is, you have to

1292
01:21:07,500 --> 01:21:13,080
have looked at the very long schedule. I mean,
there's usually, what, 65 different dev rooms,

1293
01:21:13,592 --> 01:21:14,572
[PETER] Yeah, you got to go with that.

1294
01:21:13,700 --> 01:21:14,100
[CLAIRE] so.

1295
01:21:14,672 --> 01:21:17,312
[PETER] You come, yeah, got to come
in with a tight plan nowadays, yes.

1296
01:21:17,660 --> 01:21:18,860
[CLAIRE] Absolutely. I remember.

1297
01:21:18,691 --> 01:21:22,392
[PETER] But you can also go to these
fringe events nowadays. I mean.

1298
01:21:22,440 --> 01:21:24,300
[CLAIRE] Right, the days before, the days after.

1299
01:21:23,172 --> 01:21:27,092
[PETER] The PGDay is a fringe event, but
there's also other things going on, right,

1300
01:21:28,272 --> 01:21:29,072
before and after, like

1301
01:21:29,812 --> 01:21:30,372
other meetings.

1302
01:21:31,900 --> 01:21:34,240
[CLAIRE] But you're right. You need a typed plan.

1303
01:21:34,480 --> 01:21:39,300
You can't just show up and wander around
and land in the right place. It's big.

1304
01:21:39,600 --> 01:21:43,220
It's on a college campus, so it's
spread across different buildings with

1305
01:21:43,940 --> 01:21:46,900
slush and snow on the ground
in between the buildings. And

1306
01:21:47,620 --> 01:21:49,080
so you have to have a plan.

1307
01:21:49,540 --> 01:21:53,080
I remember being very impressed by Floor
Drees one of the first times I met her

1308
01:21:53,120 --> 01:21:55,240
at FOSDEM. She showed me her spreadsheet

1309
01:21:55,720 --> 01:21:59,060
that showed where she needed to be at
all the different times, and she'd put a

1310
01:21:59,120 --> 01:22:02,920
lot of thought into it, into, you know,
what she was going to spend time on.

1311
01:22:04,960 --> 01:22:08,640
When you said random room for another
project, was it really random or did you have

1312
01:22:08,680 --> 01:22:08,980
a plan?

1313
01:22:10,632 --> 01:22:15,432
[PETER] Well, you go in with it.
Well, sometimes you go into something.

1314
01:22:16,032 --> 01:22:19,492
I mean, you come with, you have to have
a plan, but you sometimes sit somewhere

1315
01:22:21,272 --> 01:22:24,452
and just say, I will just, I'll just listen
to this because there's nothing else going

1316
01:22:24,492 --> 01:22:27,032
on right now, and this seems kind of
interesting. But then you just learn

1317
01:22:27,752 --> 01:22:30,912
sort of incredibly, I mean, a lot
of these are the dev rooms, right?

1318
01:22:31,772 --> 01:22:35,192
That are, they go sometimes
incredibly deep about things.

1319
01:22:35,872 --> 01:22:40,152
I still remember, years and years ago,
I was in the GCC dev room, but which

1320
01:22:40,532 --> 01:22:41,092
I have no...

1321
01:22:42,052 --> 01:22:46,272
obviously, I'm a user of, but I have
no real knowledge of the internals, but

1322
01:22:46,792 --> 01:22:48,012
it was just sort of seeing the

1323
01:22:49,152 --> 01:22:53,052
depth of knowledge and the enthusiasm, and
also just seeing some of the people who I

1324
01:22:53,112 --> 01:22:55,812
know worked on it, right? I just knew them as a...

1325
01:22:57,332 --> 01:22:59,732
I know they are the GCC developers,
but they don't know me, right?

1326
01:22:59,792 --> 01:23:02,832
So I'm like almost a little bit of
a fan there or something like that.

1327
01:23:05,152 --> 01:23:06,812
So stuff like that, or we were also

1328
01:23:07,272 --> 01:23:11,792
some years ago in, I think might have also
been compilers or GCC, where someone was

1329
01:23:11,832 --> 01:23:13,932
talking about developing a COBOL compiler.

1330
01:23:15,112 --> 01:23:19,052
And in some weird, bizarre, I have, you
know, no interest in that really, but in

1331
01:23:19,112 --> 01:23:23,532
some weird, strange way, they were
facing essentially the same problems that

1332
01:23:24,132 --> 01:23:30,272
we are facing developing effectively an SQL
compiler. Sort of made sense in retrospect.

1333
01:23:30,412 --> 01:23:32,152
So, but it's just like you pick up some

1334
01:23:33,072 --> 01:23:35,532
stuff like that, and still
remember that years later.

1335
01:23:36,140 --> 01:23:40,220
[CLAIRE] Okay, so shout out
to FOSDEM and FOSDEM PGDay.

1336
01:23:40,500 --> 01:23:45,460
News for 2027 is that for the first
time, I believe, FOSDEM PGDay is going to

1337
01:23:45,500 --> 01:23:49,340
be a two-day fringe event. It's always
been just a one-day fringe event.

1338
01:23:47,452 --> 01:23:47,992
[PETER] That's true, yeah.

1339
01:23:50,380 --> 01:23:53,620
[CLAIRE] And FOSDEM itself,
the dates are announced.

1340
01:23:53,680 --> 01:23:56,420
It's going to be the 30th and the 31st of January.

1341
01:23:57,340 --> 01:24:00,060
But there isn't a lot of info yet on the website.

1342
01:24:00,100 --> 01:24:02,000
They're evolving it and
building it out. And I think

1343
01:24:02,640 --> 01:24:06,280
maybe the call for devrooms is open
right now, or is it the call for stands?

1344
01:24:06,400 --> 01:24:08,040
Maybe the call for devrooms is closed.

1345
01:24:07,012 --> 01:24:09,232
[PETER] The call for stands and
the call for devrooms is open.

1346
01:24:09,532 --> 01:24:13,152
That's, you know, the fine
people of PostgreSQL Europe are

1347
01:24:13,632 --> 01:24:16,732
hopefully responding to those,
but I think the general public.

1348
01:24:18,072 --> 01:24:19,612
Doesn't have to respond quite yet.

1349
01:24:20,160 --> 01:24:27,040
[CLAIRE] I haven't seen the dates for P2D2, which
stands for the Prague Postgres Developer Day

1350
01:24:27,520 --> 01:24:31,600
conference, but that is usually
right before FOSDEM in Prague. And so

1351
01:24:30,152 --> 01:24:30,672
[PETER] That's right, yeah.

1352
01:24:32,080 --> 01:24:34,200
[CLAIRE] Tomas Vondra and
the other people involved.

1353
01:24:35,180 --> 01:24:40,060
I think deliberately align it with the
timing of FOSDEM to make it easy for people

1354
01:24:40,080 --> 01:24:41,960
to go to both. So we'll see where that lands.

1355
01:24:40,672 --> 01:24:44,232
[PETER] The few times I made it to the
Prague conference, also I really liked it a

1356
01:24:44,272 --> 01:24:48,472
lot. Unfortunately, because
of the way they time it.

1357
01:24:49,352 --> 01:24:50,592
Right before FOSDEM, I've...

1358
01:24:51,492 --> 01:24:55,132
you know, some people do the trip from
go to Prague and directly to Brussels.

1359
01:24:55,252 --> 01:24:56,232
I've never really

1360
01:24:57,252 --> 01:24:58,132
wanted to do that.

1361
01:24:59,780 --> 01:25:04,000
[CLAIRE] You just reminded me of another way you
contribute to the Postgres project, which is some

1362
01:25:04,080 --> 01:25:05,600
years, and I know it's not always you.

1363
01:25:05,740 --> 01:25:10,300
I know Daniel Gustafsson, Jonathan Katz, Melanie
Plageman, there's other people that have done it as

1364
01:25:10,360 --> 01:25:13,380
well. But some years you organize

1365
01:25:14,020 --> 01:25:18,160
one of the Postgres developer meetings, one or
both, because there's usually one coincident with

1366
01:25:18,200 --> 01:25:22,960
FOSDEM, and then there's another one tied
to PGConf.dev usually, so twice a year.

1367
01:25:23,860 --> 01:25:27,300
So, I mean, that takes work and
effort and planning and thought.

1368
01:25:24,822 --> 01:25:25,482
[PETER] That's true, yeah.

1369
01:25:27,282 --> 01:25:28,482
That does take a lot of work, yeah.

1370
01:25:29,100 --> 01:25:34,040
[CLAIRE] So figuring out what people need to
talk about, who should come prepared, etc.

1371
01:25:33,982 --> 01:25:34,342
[PETER] That's right.

1372
01:25:34,880 --> 01:25:39,480
[CLAIRE] Okay, but you answered FOSDEM and
FOSDEM PGDay as a favorite Postgres conference.

1373
01:25:39,820 --> 01:25:43,080
Do you want to give a second shout-out to
anything else that you would recommend a

1374
01:25:42,862 --> 01:25:46,202
[PETER] I already gave a shout-out to
PGDay Lowlands here, honorable mention, so.

1375
01:25:43,120 --> 01:25:43,460
[CLAIRE] listener?

1376
01:25:46,720 --> 01:25:50,260
Yeah, and Floor Drees heard you, and I
think she wants to quote you publicly.

1377
01:25:52,860 --> 01:25:57,340
So there's that. And then before
we wrap, my last question was,

1378
01:25:57,800 --> 01:26:02,040
do you have any favorite
Postgres blogs that you read

1379
01:26:02,820 --> 01:26:05,420
on a regular basis that you would
recommend to someone and why?

1380
01:26:05,760 --> 01:26:08,840
And I suppose I should say
blogs or newsletters, because

1381
01:26:09,412 --> 01:26:12,212
sometimes an aggregation of
different blog posts is useful too.

1382
01:26:14,062 --> 01:26:17,042
[PETER] I think just reading
the Planet Postgres feed.

1383
01:26:18,722 --> 01:26:20,822
I find that interesting
because that's sort of the,

1384
01:26:21,582 --> 01:26:24,822
everybody can basically register their
blog there, so you get the whole...

1385
01:26:25,702 --> 01:26:27,702
you get it from everybody, right? That's,

1386
01:26:29,002 --> 01:26:30,442
in a way, what I'm looking for, just,

1387
01:26:31,202 --> 01:26:35,002
you know, sort of serendipity,
I guess, not specifically.

1388
01:26:36,082 --> 01:26:39,962
One source, but getting sort
of this random feedback, really

1389
01:26:40,802 --> 01:26:45,042
so just to feed, or just on Mastodon,
subscribing to the hashtag Postgres.

1390
01:26:46,002 --> 01:26:48,802
Hashtag and just getting sort
of random stuff thrown your way.

1391
01:26:48,982 --> 01:26:50,423
Look.

1392
01:26:50,652 --> 01:26:54,792
[CLAIRE] I will include a link to
the Planet Postgres RSS feed in

1393
01:26:56,152 --> 01:26:57,352
the show notes for the show,

1394
01:26:58,172 --> 01:27:01,832
and it is super useful, I agree,
because so many different people,

1395
01:27:02,372 --> 01:27:05,972
authors as well as blogs, have
registered themselves there. I know that.

1396
01:27:06,732 --> 01:27:12,452
You can't, if you had a blog post about a
specific cloud implementation, a database service,

1397
01:27:13,052 --> 01:27:14,152
those don't show up there.

1398
01:27:14,631 --> 01:27:18,272
I think the Planet Postgres feed is
limited to things that are primarily

1399
01:27:19,212 --> 01:27:24,912
about the technology or open source
in nature. So it's not everything,

1400
01:27:25,472 --> 01:27:30,012
but it's a really interesting
subset, big subset. So,

1401
01:27:30,912 --> 01:27:32,852
all right, well, Peter, I want to say thank you.

1402
01:27:32,992 --> 01:27:35,352
This has been really interesting for me to

1403
01:27:36,192 --> 01:27:39,772
learn a bit more about your 25-plus year journey.

1404
01:27:40,092 --> 01:27:45,292
I think it's more like 26 or 27,
but 25 is a nice, nice even number,

1405
01:27:45,872 --> 01:27:46,852
even though it's not even.

1406
01:27:49,532 --> 01:27:52,792
I'm so glad you came on the show,
and thank you for your time.

1407
01:27:53,552 --> 01:27:56,892
Because I know you have a lot on your plate. So,

1408
01:27:57,712 --> 01:28:01,012
for those of you who are listening, if
you like today's episode and you want to

1409
01:28:01,052 --> 01:28:06,812
hear more of these Talking Postgres episodes, you
should subscribe on Apple or Spotify, YouTube, or

1410
01:28:06,832 --> 01:28:09,512
wherever you get your podcasts.
And please tell your friends.

1411
01:28:10,532 --> 01:28:13,992
If you leave a review, that'll help
even more people discover the podcast.

1412
01:28:14,512 --> 01:28:20,211
And you can always get past episodes and get links
to subscribe by going to talkingpostgres.com.

1413
01:28:20,872 --> 01:28:24,272
And you'll find transcripts included
on all the episode pages there too,

1414
01:28:24,892 --> 01:28:28,832
which are actually pretty useful for people
who do not like to listen and just like

1415
01:28:28,872 --> 01:28:30,132
to read the episodes.

1416
01:28:30,712 --> 01:28:35,092
A big thank you to everybody who joined the
live recording today and participated in the

1417
01:28:35,392 --> 01:28:36,852
live text chat on Discord.