Episode
Open Source Contributions to Postgres: The Basics
with Elizabeth Christensen
Video of a conference talk about contributing to PostgreSQL presented by Elizabeth Christensen at POSETTE: An Event for Postgres 2024. Postgres is the most advanced open-source database in the world and it's supported by a community, not a single company. So how does this work? How does code actually get into Postgres? I recently had a patch submitted and committed and I want to share what I learned in that process. I’ll give you an overview of Postgres versions and how the underlying project codebase functions. I’ll also show you the process for submitting a patch and getting that tested and committed.
Elizabeth works with Postgres Crunchy Data and is on the board of the United States PostgreSQL Association (PgUS). Elizabeth enjoys writing about Postgres for newbies and teaching people about databases whenever she gets the chance. Elizabeth hails from Lawrence, Kansas and spends most of her free time pretending like she lives on a farm in the 1860s.
Chapters
- 00:00 - Intro
- 01:19 - Why Elizabeth wanted to submit a patch
- 02:54 - The Postgres code base
- 05:23 - Key Postgres Code Teams
- 06:42 - Patch ideas
- 07:56 - Postgres Patch Process - Idea
- 08:22 - Building Postgres locally
- 10:49 - Postgres Patch Process - Testing
- 11:34 - Coding conventions
- 12:42 - Postgres Patch Process - Patch
- 15:07 - Postgres mailing lists
- 18:18 - Patch submission
- 20:09 - Patch review
- 22:58 - Getting a commit
- 24:22 - What happens next?
Recommended resources
Related episodes
Connect
- Twitter/X – @PosetteConf
- Mastodon - @posetteconf
- Threads – @posetteconf
- Subscribe to the POSETTE News
- Elizabeth Christensen | Twitter/X: @ | LinkedIn: /in/elizabeth-garrett-christensen/ | Mastodon: @sqlliz
Video of a conference talk about contributing to PostgreSQL presented by Elizabeth Christensen at POSETTE: An Event for Postgres 2024. Postgres is the most advanced open-source database in the world and it's supported by a community, not a single company. So how does this work? How does code actually get into Postgres? I recently had a patch submitted and committed and I want to share what I learned in that process. I’ll give you an overview of Postgres versions and how the underlying project codebase functions. I’ll also show you the process for submitting a patch and getting that tested and committed.
Elizabeth works with Postgres Crunchy Data and is on the board of the United States PostgreSQL Association (PgUS). Elizabeth enjoys writing about Postgres for newbies and teaching people about databases whenever she gets the chance. Elizabeth hails from Lawrence, Kansas and spends most of her free time pretending like she lives on a farm in the 1860s.
Chapters
- 00:00 - Intro
- 01:19 - Why Elizabeth wanted to submit a patch
- 02:54 - The Postgres code base
- 05:23 - Key Postgres Code Teams
- 06:42 - Patch ideas
- 07:56 - Postgres Patch Process - Idea
- 08:22 - Building Postgres locally
- 10:49 - Postgres Patch Process - Testing
- 11:34 - Coding conventions
- 12:42 - Postgres Patch Process - Patch
- 15:07 - Postgres mailing lists
- 18:18 - Patch submission
- 20:09 - Patch review
- 22:58 - Getting a commit
- 24:22 - What happens next?
Recommended resources
Related episodes
Connect
- Twitter/X – @PosetteConf
- Mastodon - @posetteconf
- Threads – @posetteconf
- Subscribe to the POSETTE News
- Elizabeth Christensen | Twitter/X: @ | LinkedIn: /in/elizabeth-garrett-christensen/ | Mastodon: @sqlliz
มีคำติชมหรือไม่? ส่งปัญหาที่เกิดขึ้นได้ที่นี่