v6.12 new traditional installation fails due to a bug in Payara dependency

In running Dataverse-Ansible to generate a SchemaSpy representation of the v6.12 database schema, we consistently hit a failed deployment, with a series of CREATE TABLE errors:

Got SQLException executing statement "CREATE TABLE EXTERNALTOOLTYPE (ID BIGINT SERIAL NOT NULL, TYPE VARCHAR(255) NOT NULL, EXTERNALTOOL_ID BIGINT NOT NULL, PRIMARY KEY (ID))": org.postgresql.util.PSQLException: ERROR: syntax error at or near "SERIAL" Position: 42

After some poking with different Payara versions, we decided that we're hitting https://github.com/payara/Payara/issues/8250 which was introduced in Payara 7.2026.6 though strangely the GitHub Actions-based tests didn't hit this same error (we tested against PG17, so the bug must somehow manifest in the RHEL-family ecosystem).

We'd like to test on Monday with payara-5.0.1.payara-p1 though I don't see it on Maven just yet.

Better solutions welcomed, more as we know it, everyone have a great weekend.

Start by reproducing the Dataverse-Ansible SchemaSpy deployment with the reported Payara versions, PostgreSQL 17, and the RHEL-family environment. Compare the GitHub Actions setup with the failing traditional installation and investigate the linked Payara issue and available payara-5.0.1.payara-p1 artifact. Done means the v6.12 schema generation completes without the CREATE TABLE syntax errors.