Small issues after migrating to Postgresql

Installation Issues
1

After migrating Passbolt to Postgresql following this guide ( https://www.passbolt.com/blog/how-to-configure-passbolt-with-postgresql-experimental - Using Option 3 ), I saw some errors in the Passbolt logs regarding the id columns in different tables.

After looking myself and asking some AIs, i saw ALL IDs where using char(36) type for them. Tho Cake excpect in Postgresql a type of uuid. After running some SQL commands to changes the IDs into a uuid type ( as well as foreign keys, like created_by ) I no longer have errors in the Passbolt logs.

If some of you have a similar issue, you can take a look at my conversation with claude to fix it ( https://claude.ai/share/350a56f0-357a-480b-8d7c-5021b0751962 )

And if possible, can the Passbolt Team add a specific migration in the migrate_postgres command to convert the id columns to uuid types, that would be perfect.

Installations informations

  • K8S install (via helm)
  • Version 5.9.0
  • Old mariaDB from the helm (iirc mariadb 10 or 11)
  • new Psql is a cloudnative PG 17 cluster
  • Using Redis
2

G’day Ibaraki.

I can confirm the bug in the migrate_postgres command. The list of migrations it re-runs hasn’t been kept in step with later refactors, so the folders tables (and a couple of others) get missed and stay as character(36) instead of native uuid. The ALTER approach you used is the right workaround in the meantime.

We’re tracking the task to fix it as PB-50293

I’ll update this thread when it’s live.

Cheers
Gareth