postgres@hacking:~$ man postgres-hacking
A public workshop for hacking Postgres.
We pick real problems, inspect the code, prototype fixes, test the ugly edges, and push useful work toward -hackers and CommitFest.
Why “Postgres Hacking”?
It works as the community and site name. “Hacking Postgres” remains the session-series title used by PostgresTV. Both point to the same work.
How to contribute
- Join the Telegram group and pick an open work line.
- Read the patch, thread, and current blockers before writing code.
- Reproduce first. Add tests. Measure observer effects.
- Post durable results to GitHub, -hackers, or CommitFest.
~/postgres-hacking/README
$ values
public evidence > recollection
tests > confidence
small patches > grand plans
review is work
$ status
7 open lines
blockers visible
community online
Research note: generic-title sessions without descriptions remain deliberately unmapped unless a same-day artifact or another public source identifies the topic. We do not manufacture provenance.