Quarkus JDBC EDB

Add the extension to your build file. With Maven, add the following dependency to your POM file:

This extension requires Java 17 or later and Quarkus 3.33 or later.

Every commit is built and tested on JDK 17, 21 and 25, and an application is built against the oldest supported Quarkus version to verify it stays usable there.

Native image builds are verified on JDK 17 only. That is not a limitation of native image support: the native build uses a Mandrel builder image with its own bundled JDK, so it is insensitive to the JDK used to run the build. Note that Quarkus 3.39 raises the minimum GraalVM/Mandrel version to 25.0, which matters when building native images rather than when running them.

Two things differ from PostgreSQL and catch people out:

Because this extension is usually the only JDBC driver on the classpath, quarkus.datasource.db-kind may be omitted entirely and will resolve to edb.

This extension contributes no configuration properties of its own; it is configured entirely through the standard Quarkus datasource configuration.

This uses com.edb.xa.PGXADataSource.

db-kind=edb maps to Hibernate ORM’s org.hibernate.dialect.PostgresPlusDialect, the dialect written for EDB Postgres Advanced Server. No further configuration is required — in particular, do not set quarkus.hibernate-orm.dialect manually.

Encrypted connections need no extra configuration beyond the driver’s own properties on the JDBC URL:

sslmode=require encrypts the connection without validating the server certificate; verify-full additionally verifies the certificate chain and the hostname. Mutual TLS is supported by adding a client certificate and key:

The client key must be in PKCS#8 DER format — the driver cannot read a PEM key:

All of these work in native mode as well as JVM mode.

Flyway works against EPAS, but needs two things that are easy to miss.

First, add the PostgreSQL database module. Since Flyway 10 each database lives in its own artifact, and quarkus-flyway depends only on flyway-core. Migrations fail without this module regardless of which database you use:

Second, add changeServerName=true to the JDBC URL:

Flyway selects its database type from the product name reported through JDBC metadata and ships no type for EnterpriseDB, which is what EPAS reports. Without this property migration fails with:

Note that changeServerName=true changes what every reader of DatabaseMetaData sees, not just Flyway. The Hibernate dialect is unaffected, because Quarkus resolves it at build time from the db-kind, but application code branching on getDatabaseProductName() will see PostgreSQL. Liquibase is affected in particular — see Liquibase.

Liquibase works against EPAS with no additional configuration. Unlike Flyway, it ships a database implementation for EnterpriseDB and selects it automatically, which you can see at startup:

For that reason, do not set changeServerName=true when using Liquibase. It makes the driver report PostgreSQL, so Liquibase selects its generic PostgreSQL implementation and loses the EDB-specific handling shown above.

If an application uses both Flyway and Liquibase against the same datasource, these requirements conflict: Flyway needs changeServerName=true, and Liquibase is better without it.

Native image compilation is supported and needs no additional configuration:

The EDB driver is a fork of pgjdbc and connects to a community PostgreSQL server, which is useful for local development and is how this extension’s own integration tests run in CI. Be aware of what is not present there:

Note that the Hibernate dialect is selected at build time from the db-kind, so PostgresPlusDialect is used in both cases.

The com.enterprisedb:edb-jdbc driver is published on Maven Central under a dual licence: BSD-2-Clause and the EDB Limited Use Software License Agreement. Review both before deploying.