Open Source Contributions to Postgres: The Basics
summary
A concrete how-to showing a real documentation patch that actually gets committed, explaining why the HOT updates docs needed clarifying about BRIN interaction and how that fix was built and tested locally using Meson and Ninja plus docbook for the docs, packaged as a git patch workflow and sent to mailing lists and Commitfest. Expect practical details on running the regression tests, the patch header format, and project scale — roughly ~300 patches, ~26% committed so plan for extensive review and patience.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:19Why Elizabeth wanted to submit a patch
- 2:54The Postgres code base
- 5:23Key Postgres Code Teams
- 6:42Patch ideas
- 7:56Postgres Patch Process - Idea
- 8:22Building Postgres locally
- 10:49Postgres Patch Process - Testing
- 11:34Coding conventions
- 12:42Postgres Patch Process - Patch
- 15:07Postgres mailing lists
- 18:18Patch submission
- 20:09Patch review
- 22:58Getting a commit
- 24:22What happens next?
related talks
50mHacking on Postgres: An Overview
42mMy Journey in PostgreSQL bug fixing
50mPostgreSQL hacker tips
47mMy Journey in PostgreSQL bug fixing
47mBeginner's guide to PostgreSQL Hacking
07mKeynote: Contributing to Critical Open Source Projects: Lessons from PostgreSQL
48mWhat's in a Postgres major release?...
12mContribution Over Control Open Source Responsibility in PostgreSQL