1
I'm a developer diving deep into PostgreSQL internals, aiming to contribute meaningfully to the project. I have a strong grasp of core components like the internal architecture, physical replication, WAL (Write-Ahead Logging), and buffer management. I'm now expanding into areas like logical replication, asynchronous I/O (AIO), the optimizer, and beyond.
To learn and grow as a Postgres hacker, I want to hear directly from you—PostgreSQL users—about the problems you face, big or small. These could be operational challenges, performance bottlenecks, confusing behaviors, missing features, or friction points in your workflows.
For me, it's a win-win: you get a contributor trying to tackle real problems, and I get to deepen my understanding by working on issues that matter in the real world. If a problem resonates with me, I’ll do my best to investigate, learn, and potentially create a patch to address it.
Thanks—and I look forward to hearing from you!
I'm 24 and have been diving into Postgres internals and learning about other database systems since I was 21. I'm deeply fascinated by systems programming and database architecture — especially how things work under the hood.
I'm trying to shape a long-term career in this space, and I'd really appreciate hearing from folks with more experience. A few questions I’ve been reflecting on:
1)What are some things you wish you had done earlier in your journey?
2)What are some things you wish you hadn’t spent time earlier on?
3)What keeps you motivated or helps you push through when you’re stuck or feeling low?
Any advice, reflections, or stories would mean a lot. Thanks in advance!