Interview with EDB
Find out more about EDB
Any views or opinions represented or expressed in this interview belong solely to the interviewee and do not neccessarily represent those of the PGDay Lowlands 2026 organisation, PostgreSQL Europe, or the wider PostgreSQL community, unless explicitly stated.
Describe your company in brief and tell us how its core values align
with those of the Postgres community.
EDB is a private software and services company centered entirely around the PostgreSQL database ecosystem. Founded in 2004, EDB provides enterprise-grade tools, 24/7 global support, advanced security, high availability, and database compatibility tools (notably for migrating away from Oracle).
EDB embraces a multi-vendor, distributed development model. We employ several PostgreSQL Core Team members, Committers, and other contributors who work openly on community mailing lists alongside competitors to build consensus. We view the health of the open-source Postgres ecosystem as directly tied to its own (and our own) commercial success. By actively contributing upstream rather than just pulling downstream, EDB bridges the gap between raw community innovation and enterprise expectations.
Where is PostgreSQL going to achieve a lot of progress in the next few
years? Will your company be a part of it as a contributor?
PostgreSQL is undergoing a profound structural shift. It's no longer just the industry’s trusted transactional database, Postgres is rapidly evolving into a unified platform for enterprise AI, globally distributed architectures, and analytical processing. At EDB, we actively feed the innovations from our EDB Postgres AI platform back into the upstream community. By driving foundational projects like WarehousePG, CloudNativePG, and Barman, we aren't just participating in this evolution—we are building the architecture for it.
Name the most valuable contributions that your company has shared with
the community? What makes each of them special?
Notable features our team contributed to PostgreSQL over the years include incremental backup in PG 17, by Robert Haas, OAuth in 2025, by Jacob Champion, and Dynamic Extension Loading that same year - certainly solving an industry-wide issue.
Key historic contributions include Pavan Deolasee’s Heap-Only Tuples (HOT) in PostgreSQL 8.3, and Vadim Mikheev’s foundational work on Write-Ahead Logging (WAL). While WAL of course predates EDB's founding, we are proud to employ the very pioneers who shaped the project's history.
Beyond these core features, EDB engineers maintain massive open-source ecosystem tools like pgAdmin (the leading graphical management tool) and Barman (backup/disaster recovery manager). We're also the original creators of the CloudNativePG project, the de facto Kubernetes operator for PostgreSQL.
As the PostgreSQL project turns 30 this year, Bruce Momjian, Core team member, celebrates 20 years at EDB!
Why did you choose to support PGDay Lowlands this year? What makes this
conference special?
From day one, we’ve been proud supporters of PGDay Lowlands! Our very own Boriss Mejias and Floor Drees put their hearts into making this conference incredible, and we love standing behind them. The Dutch PostgreSQL community has such a powerful spirit; between the local hackers and the strong representation at European events, the energy is unmatched. We can't wait to connect with the community in the Netherlands again!
What does your company do for the PostgreSQL project and the tech
community around it?
Beyond code contributions our team members contribute by maintaining package managers, participating in different committees and working groups, organizing community conferences, and freely sharing their knowledge through talks and workshops.
What is your team’s most anticipated feature in the next major release
of PostgreSQL and why?
Álvaro Herrera, with Mihail Nikalayeu and Antonin Houska (Cybertec) might very well see their work on REPACK CONCURRENTLY go into the next release. Álvaro and Antonin teased this functionality at last year’s PGConf EU, in Riga. The pitch? REPACK goes further where VACUUM FULL falls short, removing table bloat without locking tables.
What needs to be done for PostgreSQL to keep leadership in the database
space?
Let’s be a little cheeky and pair this with another critical question on your list: "What approach will make Postgres thrive in an AI-driven world?" The answer is two-fold. First, Postgres must deliver elite performance for modern AI workloads. Second—and perhaps more challenging—the community must learn to seamlessly manage, review, and benefit from the influx of AI-assisted patches and reviews. If the open-source community can successfully navigate this new frontier of development, the sky is the limit (or, more accurately, the CPU).
