Camunda 7.19 compatibility with Postgresql 15 is KO

Camunda 7 Topics Discussion & Questions
1

I have tested a docker image of Camunda 7.19 with external PosteGreSql driver.
The auto boot works fine with Postgre 14 but fails with Postgre15.
The root cause is related to a change of the default user privileges in Postgre15.
The boot process of Camunda should take into account this change.
Wish it helps

2

Hi @qualitesys,

Could you please share steps to reproduce the issue and stacktrace of the failure?
I managed to start Camunda Run + PostgreSQL 15 without facing any problem.

Best regards,
Yana

3

I have made 2 tests.
1 - create a managed PostGreSql 15 database at OVHCloud, then create a serverless container at Scaleway (docker image of camunda run camunda/camunda-bpm-platform:run-latest) with environment variable for database url pointing to the OVHCloud database (example jdbc:postgresql://postgresql-aaaaaaaaaa.database.cloud.ovh.net:20184/camunda?sslmode=require). It fails
2 - the same with a Scaleway Managed database. It fails
3 - the same with a AWS Managed database. It fails

So I tried the same tests with PostGreSql 14, everything is fine for the 3 Cloud providers
The problem comes from the default user rights in PostGreSQL 15, specialy for creating the initial Camunda tables. The user has no rights for it, the Camunda startup fails.
Wish it helps
Didier

4

CREATE USER camunda PASSWORD ‘camunda’;
ALTER USER camunda CREATEDB REPLICATION;

  • CREATE DATABASE camunda ENCODING = ‘unicode’; (pg14)
  • CREATE DATABASE camunda WITH OWNER camunda ENCODING = ‘unicode’; (pg15)
    GRANT ALL PRIVILEGES ON DATABASE camunda TO camunda;

Postgres 15 requires to add “With owner camunda”. It is change from 14 to 15