The ezp5 configurations in app/config now take precedence over (some?) legacy settings. This causes an issue with PostgreSQL handling (and possibly other handlers/engines) when a valid database type in ezp5 does not correctly map to a known/valid database handler in ezp legacy.

Example:

ezp5 knows the following database types: mysql, sqlite, pgsql
ezp legacy knows the following database handlers: mysql, mysqli, postgresql, ezpostgresql, etc...

Solution for pgsql:

$ settings/site.ini

[DatabaseSettings]
ImplementationAlias[pgsql]=eZPostgreSQLDB