PostgreSQL hacker tips
summary
Collection of shell-driven tricks and reproducible setups: a home dotfiles repo plus scripts like PG_compile to build many branches and PG_check to run full regression suites quickly, helpers to spawn/kill nodes and run pg_upgrade, and per-version aliases so five–six releases (and historic 9.5/9.6) stay ready. Use git format-patch, commitfest workflow and CI to validate patches. Enable use-clobber-cache and 32-bit/Windows emulation to catch use‑after‑free and platform bugs. Expect 40–50 OpenSSL/version builds for some patches and maintainers juggle across six branches.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 4:02PostgreSQL community process
- 13:16Development environment setup
- 25:16Internal PostgreSQL tricks
- 37:36Testing and CI practices
- 43:00Being a PostgreSQL committer
- 46:31Q&A session
related talks
47mBeginner's guide to PostgreSQL Hacking
50mHacking on Postgres: An Overview
51mWhen Postgres Can't, You Can!
01h 00mThe 10 Deadly PostgreSQL Sins
46mPostgres Platform "Best Practices" for the Modern DBA
44mBenchmarking your commits: The Postgres Performance Farm
56mPostgreSQL at low Level: stay curious!
50mSecuring PostgreSQL