IVAN LUMINARIA

Oracle, PostgreSQL & MySQL Expert | DWH Architect | Project Manager

IT professional with approximately 30 years of experience in designing, implementing and managing database and Data Warehouse solutions across Oracle, PostgreSQL and MySQL environments.

LinkedIn: ivanluminaria
Email: ivan (dot) luminaria (at) gmail (dot) com

I have been working with databases for about thirty years.

Long enough to have seen engines, languages, trends and buzzwords change.
Long enough to know that beneath the surface, the rules never really do.

A database is not a container.
It is an organism.
It breathes.
It gets tired.
It locks.
Or it scales.

I started in Oracle mission-critical environments, when “mission-critical” wasn’t a slide-friendly expression.
It meant the difference between a system holding up — or collapsing at three in the morning.

I’ve spent countless hours on AWR, ASH, execution plans.
I’ve seen systems slow down “for no apparent reason.”
And I learned that there is always a reason.
You just have to look for it methodically.

Then came PostgreSQL and MySQL.
Different tools.
Different philosophies.
Same discipline.
Understand the engine.
Don’t fight it.

I don’t believe in magical tuning.
I believe in up-to-date statistics.
In sound data modeling.
In the difference between “it works” and “it holds.”

Because a slow database is not a technical issue.
It’s a business issue.
It’s a report that doesn’t arrive.
A customer who waits.
A decision made too late.

And that’s exactly where I like to be —
where technology meets real impact.

How I Work #

I don’t just “administer” databases.

I observe them.
I measure them.
I stress them.
I secure them.

I focus on performance tuning in complex environments — Oracle, RAC, Exadata — as well as PostgreSQL and MySQL in modern, often open-source contexts, where the lack of proprietary “magic” forces you to truly understand what happens under the hood.

I design Data Warehouse architectures because data is not meant to be stored.
It is meant to be understood.

I’ve worked with multidimensional models, ETL/ELT processes and data flows that must be reliable before they are fast.
Because incorrect data, even delivered in milliseconds, is still incorrect.

I write PL/SQL when needed.
I optimize when required.
I refactor when inevitable.

I’m not interested in flashy effects.
I’m interested in solidity.

Vision #

Over the years, I have combined deep technical expertise with broader perspective.

I have coordinated small international teams.
Translated business requirements into sustainable technical decisions.
Learned that complexity cannot be eliminated.
It must be governed.

Agile, Scrum, structured processes — useful tools.
But without real competence, they remain labels.

For me, leadership means something simple:
making technical decisions that stand the test of time.

Beyond the Database #

Outside of work, I cultivate passions that, in many ways, speak the same language.

Photography taught me that the right light changes the story.
Music — I’m learning the saxophone (with patience and humility) and playing guitar — reminds me that technique without sensitivity is just noise.
Cooking is edible architecture: balance, timing, proportion.
Chess is pure strategy: every move is a choice, every choice has consequences.

Perhaps that’s why I feel comfortable in complex systems.
They don’t intimidate me.
They intrigue me.

I like going deep into details.
But only to make the whole work better.

I don’t build databases.
I build solidity.

“I transform data complexity into strategic business value.”