PostgreSQL Conference Europe 2026

PostgreSQL creates value for our customers through the strength and flexibility of its open source ecosystem. It is more than a database, it is a broad environment of tools, extensions, and deployment options that gives users tremendous choice, but can also be difficult to navigate.

This is where companies like Percona add value. We help customers identify the right technologies for their needs, simplify complex choices, and operate PostgreSQL with confidence. By understanding the challenges our customers face, we can also advocate for the features, improvements, and solutions the wider PostgreSQL community needs.

For more than 20 years, Percona has been an advocate for open source databases and the communities that sustain them. We began with MySQL and later expanded our focus to other open source databases as customer needs evolved.

PostgreSQL was a natural addition to our offering. It is one of the most capable, widely adopted, and respected open source databases available today. And, after all, when people think of open source databases these days, it is increasingly difficult to ignore the elephant in the room.

We are particularly proud of our work on Transparent Data Encryption through the pg_tde extension. This capability had been discussed in the PostgreSQL community for more than a decade, yet there was still no fully open source solution available to users.

We believe that compliance-critical capabilities such as encryption should not be confined to proprietary offerings. We would not be true to Percona’s mission if we did not challenge that status quo. By introducing pg_tde, contributing it openly, and continuing to develop it with the community, we are helping make enterprise-grade security available to every PostgreSQL user, not only those prepared to accept a vendor lock-in.

Rather than one missing feature, we see two areas where PostgreSQL would benefit from a clearer standard.

The first is horizontal scaling. The ecosystem offers a range of solutions, but there is still no single approach that can be confidently recommended to most users as the obvious default. As PostgreSQL adoption continues to grow, horizontal scaling is one of several areas where the community would benefit from a broadly accepted gold standard.

The second is more comprehensive auditing. Users coming from proprietary databases often expect detailed records of who created or modified every database object, what changed, and when. Providing that level of visibility more consistently would make PostgreSQL an even stronger choice for organizations with demanding governance and compliance requirements.