1) Let’s start with you!
Tell us a bit about yourself – your background, current role, and what excites you most in the world of tech.
I’m Nisha, a software developer at Fujitsu, working deep in the internals of PostgreSQL. I spend my time writing C, breaking things, fixing them, and contributing patches and features to the core—sometimes reviewing others’ work too. What excites me most is building smarter, more resilient distributed systems—especially when it comes to replication, consistency, and conflict resolution.
2) Why PostgreSQL?
What inspired you to explore or switch to PostgreSQL?
I started with PostgreSQL when I joined Fujitsu about one and a half years ago. Once I started working on it, I got pulled in by how powerful and elegant it is under the hood. The more I explored its internals—especially replication—the more it fascinated me. It’s not just a database, it’s an entire world of design choices, performance challenges, and open-source brilliance.
3) What are you working on with PostgreSQL right now?
Share the cool stuff you’re building, learning, or solving using PostgreSQL.
Currently, I’m working on conflict detection and resolution for logical replication. I recently developed a solution for detecting multiple_unique_conflicts, which has been committed to PostgreSQL 18. I was also involved in introducing another PostgreSQL 18 feature that automatically invalidates replication slots based on activity timeout.
4) What’s been your biggest learning or challenge on this journey?
A lesson, mistake, or an aha moment, we’d love to hear about it!
One of my biggest challenges was getting comfortable with the PostgreSQL codebase—it’s vast and layered, and at first, I often felt lost. Every time I thought I understood how something worked, an edge case would show up and flip that understanding. But over time, I learned to navigate the system with more confidence. Those “wait, that’s how it works?!” moments turned out to be the most rewarding part of the journey.
5) Your wisdom to rookies like yourself?
What’s one tip or piece of advice you’d give to someone just starting out with PostgreSQL?
Start by using PostgreSQL, then slowly lift the hood. Follow the -hackers mailing list and pick one subsystem—like the optimizer or replication—to explore in depth. Don’t hesitate to ask questions, report bugs, or even propose fixes and features. The PostgreSQL community is more welcoming than you might expect.
6) Finally, describe your PostgreSQL journey in one word. Yep, just one!
Transformative – It’s reshaped how I think and build systems.
7) Who or what has influenced your PostgreSQL learning the most?
A mentor, a community, a course, a project, tell us what or who helped you grow.
Definitely the people around me. My whole team at Fujitsu is incredibly talented, and I learn something new from them every single day. Special mention to Amit Kapila, Vigneshwaran C, and Shveta Malik—their depth of knowledge and willingness to share it has shaped a big part of my PostgreSQL journey.
8) What’s one PostgreSQL concept or feature you finally understood and felt proud of?
That lightbulb moment when something clicked, we all have one!
Replication slots. At first, they felt like dark magic—but once I understood the underlying concepts and how they preserve WALs to ensure subscriber consistency, everything clicked. Eventually, I got to work on features to make them even more robust, which made the journey feel full circle.
