21.1.20230210 postgres with scram-sha-256 database error

[hawkjast]

EGroupware 21.1.20230210
Debian GNU/Linux 11 (bullseye)
ii php7.4 7.4.33-1+deb11u4
ii postgresql-13 13.11-0+deb11u1

After changing postgres authentication method from md5 to scram-sha-256:

/var/www/egroupware/api/src/Egw.php (120)
Database error
It appears that you have not created the database tables for EGroupware.

Reverting scram-sha-256 -> md5 solves problem, but I think you’ll agree that it’s temporary.
scram-sha-256 will be default after postgres upgrade from 13 to 15 in Debian 12 bookworm.
Is scram-sha-256 support planned in EGW?
I plan on dist-upgrading soon…

[RalfBecker]

Please keep in mind, that EGroupware currently only supports PostgreSQL < 12, see https://github.com/EGroupware/egroupware/wiki/Distribution-specific-instructions#postgresql

There are currently not plans or Budget to change that.

This has deeper technical reasons: OIDs have been dropped in PostgreSQL 12 and they have been used in EGroupware/ADOdb to retrieve automatic IDs created during inserts.

Ralf

[hawkjast]

Sad to read, used EGW many years since early versions.
Other than the minor stuff with node&npm, I had no problems with self-hosting EGW on my debianes since etch (4.0 year 2007).
Postgres is excellent backend free from problems with utf8mb4.
Looking at:

Clue to migrating from Postgresql to Mysql

See many problems with backup&restore variant.
This one looks old:

Database convertions, registration

Will work with 21.1 family?
Is there safe and reliable procedure to migrate from-postgresql-to-mysql?
(didn’t found “success stories”)

[RalfBecker]

The migration from PostgreSQL to MariaDB (or MySQL) is really easy:

1. Create a new container based default installation
2. take a DB-backup on the old system
3. rsync /var/lib/egroupware/default to the new system
4. restore the backup you taken in step 2.

Let me know, if you run into any problems.

Ralf