We’re excited to share that our recent test run using the Postgres Compatibility Index (PCI) achieved 100% compatibility.
PGScorecard – PostgreSQL Compatibility Index appeared first on MariaDB.org
We’re excited to share that our recent test run using the Postgres Compatibility Index (PCI) achieved 100% compatibility.
The PCI was created to bring clarity to the often used but loosely defined term “PostgreSQL compatible.” As Mayur explains in his article The Making of ‘Postgres Is’, the goal is simple: to ensure that when a system claims to be compatible with PostgreSQL, it truly behaves like upstream PostgreSQL in practice. The PCI accomplishes this by running a comprehensive set of tests across features like data types, procedural functions, constraints, extensions, and more, and producing a measurable, transparent score. This gives users and vendors a reliable benchmark rather than relying on marketing claims.
Compatibility matters because many organizations rely on PostgreSQL variants, repackaged distributions, or vendor supported systems. They want the confidence that their schemas, tools, extensions, ORMs, client libraries, and workflows will continue to work as expected. A system that drifts from upstream PostgreSQL can introduce subtle risks such as, unsupported features, migration challenges, and vendor lock-in.
Achieving a perfect PCI score means our system supports the full baseline feature set as currently defined. It demonstrates that users can rely on the same behavior as community PostgreSQL, whether they are self-hosting, using a vendor-supported version, or integrating with existing tools. Importantly, it also shows that you can have a fully open-source system while still benefiting from vendor support, without compromising compatibility.
In a world where “PostgreSQL compatible” is often a vague claim, initiatives like the PCI provide the needed help with transparency and comparability. It helps to protect you from marketing claims in the PostgreSQL ecosystem, ensuring that tooling, and workflows continue to function reliably.
Special thanks to Mayur, whose initiative is helping define a clear, standardized framework for PostgreSQL compatibility.
The test run was done against Percona Server for PostgreSQL 17.6.1. Click for test result. Percona Server for PostgreSQL is a binary-compatible, open source drop-in replacement for PostgreSQL with the currently needed enhancements, to make Transparent Data Encryption (TDE) work.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | A thread through my 2025 Postgres events | 0 | 7.52 | 10-11-2025 |
| 2 | Open source, PostgreSQL, and risk mitigation in an era of acquisitions | 0 | 5.19 | 19-12-2025 |
| 3 | Learn PostgreSQL and SQL Quickly and Free | 0 | 3.51 | 20-05-2024 |
| 4 | Why PostgreSQL needs an AI usage policy | 0 | 6.85 | 26-06-2026 |
| 5 | TDE performance in PostgreSQL | 0 | 5.98 | 20-07-2026 |
| 6 | Say Hello to OIDC in PostgreSQL 18! | 0 | 7.89 | 22-10-2025 |
| 7 | PostgreSQL minor release postponed in Q1’ 2026 | 0 | 8.34 | 18-02-2026 |
| 8 | The Ins and Outs of PostgreSQL Default Configuration Tuning | 0 | 6.18 | 31-03-2022 |
| 9 | PostgreSQL Autovacuum Internals and Benchmark | 0 | 4.74 | 01-07-2026 |
| 10 | PostgreSQL 18 OIDC Authentication with Ping Identity using pg_oidc_validator | 0 | 12.43 | 04-03-2026 |