Jessica Shelar - Rookie of the Month March 2026

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.

Hi, I’m Jessica Shelar currently working as a Database Developer at DataCloudGaze Consulting where I focus on developing migration patterns to transition databases from Oracle to PostgreSQL. Alongside, I’m finishing my master’s in information technology from Ramnarian Ruia College. What excites me most about the world of technology is how fast-paced and constantly evolving it is there’s always something new to learn, innovate, and improve, which keeps me motivated and curious every day. 

2) Why PostgreSQL? What inspired you to explore or switch to PostgreSQL?


I first got introduced to PostgreSQL at DataCloudGaze, a big part of my work involved migrating databases from Oracle to PostgreSQL, so I began using it hands-on in real-world projects. That practical exposure helped me understand not just the syntax differences, but also architectural considerations and performance tuning aspects. I was also fortunate to have a great mentor who guided me really well during this process. Their support helped me understand best practices, migration strategies, and how to think critically about database design rather than just writing queries.

3) What are you working on with PostgreSQL right now?

Share the cool stuff you’re building, learning, or solving using PostgreSQL.

At DataCloudGaze, I’m working on enhancing our internal migration tool, DCGMigrator, primarily by developing and applying patches to improve its stability and efficiency. A big part of my focus is optimizing Oracle-to-PostgreSQL migration workflows making them more predictable, performance-aware. 

In parallel, I’m building performance monitoring utilities using MCPToolbox to streamline our day-to-day database tasks. This includes automating diagnostics, improving visibility into query performance, and helping the team proactively identify bottlenecks. The goal is not just migration, but making the overall development and database optimization process smoother and more structured.

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 the most biggest challenges has been handling PL/SQL packages with global variables. In Oracle, package-level global variables are commonly used to maintain state across procedures within a session. PostgreSQL doesn’t support package-level global variables in the same way, so we can’t directly replicate that behavior. I worked on redesigning that logic either restructuring it using schemas and separate functions, or handling state management differently at the application or session level. 

5) Your wisdom to rookies like yourself?

Consistency will take you a long way. Start by mastering SQL fundamentals first having a strong foundation makes everything else much easier. The PostgreSQL community is incredibly supportive, so don’t hesitate to ask questions or seek guidance. When I gave my first talk, I was extremely nervous. But the community was welcoming and encouraging, and they even provided constructive feedback on how I could improve. All you really need is dedication and the willingness to keep learning.

6) Finally, describe your PostgreSQL journey in one word.

Yep, just one!

Sublime

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.

My PostgreSQL journey began under the guidance of the Founder and CEO of DataCloudGaze Consulting, Deepak Mahto, who has been the biggest influence on my learning. He mentored and taught me not just how to use PostgreSQL, but how to truly understand it, from an architectural and performance perspective to thinking critically about database design. Beyond mentorship, working on real-world projects further accelerated my growth. But the initial guidance and mindset he instilled have been the most impactful in my journey so far.

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!

One PostgreSQL concept that truly gave me a lightbulb moment was partition pruning and the importance of using EXPLAIN ANALYZE. Initially, I understood partitioning as just a way to split large tables for manageability. But when I started analyzing execution plans, I realized how powerful partition pruning actually is. Watching PostgreSQL scan only the relevant partitions based on filter conditions rather than the entire dataset completely changed how I think about schema design and performance optimization. At the same time, learning to properly use EXPLAIN ANALYZE was a turning point. I moved from just checking if a query works to understanding how it works