Contributing to open source
PostgreSQL — Blurring the Line Between Mine and Ours
Reflections on Meaning, Growth, and Community in Open Source
As the biggest PostgreSQL community conference in Europe, PGConf.EU 2025 in Riga, Latvia, is in full swing, I feel immense pride in having been part of the small group of people who dedicated their free time to making this event a success.
In the past, I’ve organised both larger- and smaller-scale events — always as part of professional teams, where managing events was their full-time responsibility. Here, we were just ten people — each of us already juggling demanding full-time jobs outside the scope of PGConf.EU.
So why do we do it? Why do we give up precious time — time we could spend on work, hobbies, children, partners, or friends — to contribute to something we’re not even paid to do?
Why contribute to an open source project like PostgreSQL?
There isn’t one easy answer, and every person has their own. Here’s how I see it.
Finding meaning
As with any volunteering opportunity, there’s a deeper sense of meaning that this kind of work brings. Sacrificing your personal time and energy to prioritise a greater goal gives a powerful sense of purpose.
To quote Bruce Momjian, a co-founder and core team member of the PostgreSQL GDG:
“…success of the PostgreSQL project is a purpose far greater than our individual or company successes.”
In the context of PostgreSQL, that greater goal is helping the project stay at the forefront of database technology — so that it remains the open source database of choice for businesses, even when compared to commercial giants like Oracle. By contributing, we’re driving the adoption of PostgreSQL and pushing its technological edge forward.
For the majority of contributors, this work is a choice — they’re not paid for it, not legally obliged, and no one expects it from them. And that’s exactly what makes the contribution so meaningful: it’s driven by purpose, not pressure.
Belonging
Belonging is something that we all seek. The world’s longest-running study of happiness (the Harvard Study of Adult Development ) found that strong social connections are the most consistent predictor of long-term happiness and health.
Working on an open source project where people deeply believe in what they’re building creates a strong communal bond. It gives that sense of being part of something larger — of being seen, valued, and integral to the whole.
Over nearly 40 years, the number of people who make up the PostgreSQL community has grown exponentially, but the fabric of the community hasn’t changed. It’s still made up of smart, driven, and motivated individuals — champions of open source as a rightful model. It’s no surprise, then, that you might want to be part of that group.
Reputation
Inevitably, when you contribute to an open source project, you have the chance to demonstrate your commitment, professionalism, and drive — all while working alongside people you might never otherwise meet.
Over time, you begin to build a reputation outside your existing circles — beyond your workplace, your friends, or other communities you’re part of. You become “that person” — the one who knows how to get things done, who understands the process, who knows the right people to ask.
The context of open source is unique in that way: the people working alongside you aren’t doing it because they have to — and neither are you. And yet, you’ve both chosen to show up. That mutual choice speaks volumes.
Self growth
Some activities that the PostgreSQL community engages in may seem like a complex and unstructured at first glance. Whether you’re interested in contributing to the codebase or supporting the project’s operations behind the scenes, it’s often difficult to find clear entry points or understand the processes involved — if they exist at all.
Often, you’re left to discover these pathways on your own and carve out your personal route. While this can be challenging — requiring you to take on tasks you may have never attempted before — it’s also transformative. You grow as you face these challenges, adapting and evolving along the way.
If you want to introduce a patch, the first step is often “selling” your idea on the pgsql-hackers mailing list — to do this effectively you need to go beyond your technical know-how. You’ll need soft skills to communicate effectively, the persistence to review prior discussions or related patches, and the determination to build a compelling case for your proposal.
All of this requires stepping out of your comfort zone — voluntarily (and you need a heck of a lot of self-motivation to do that). You have to put yourself out there, engage with people you’ve never met, and discover what’s possible beyond your usual boundaries.
But once you do, the rewards are real: new skills, meaningful connections, and a deep sense of accomplishment — the kind you rarely get in more traditional or structured environments.
Making a difference
Not all the work we do as contributors feels remarkable at first glance, and not every task will change the course of PostgreSQL’s development or adoption.
But if you stick with Postgres over time and continue contributing, you might begin to see the difference — the impact of your work and your commitment.
And if nothing else, isn’t that something worth pursuing?
Want to get involved? We’re currently looking for new members for the PostgreSQL Europe Diversity Committee.
