Upgrading major version causes an error when using PostgreSQL 16

[smng]

Steps to reproduce the issue

Upgrade last version minor version of Joomla 4 to the next major Version 5 using PostgreSQL 16.

Expected result

Upgrade should be successful

Actual result

The upgrade process results in an error and leave Joomla in an unusable state with no possibility to login into the administration gui.

System information (as much as possible)

PostgreSQL 16
Debian 12
PHP 8.2.18
Upgrade Joomla 4.4.9 to 5.2.0

Additional comments

The reason is, that the parameter lc_collate was removed in PostgreSQL 16.
But the file administrator/components/com_admin/src/Model/SysinfoModel.php (Lines 319 and 320) try to query the value of this parameter:

'dbcollation'            => $db->getCollation(),
'dbconnectioncollation'  => $db->getConnectionCollation(),

I have comment out this two lines and the upgrade process works fine.

[alikon]

this was fixed joomla-framework/database#295 and released in

https://github.com/joomla-framework/database/releases/tag/3.2.1 but not backported in j4 which use still "joomla/database": "^2.1.1",

p.r for 2.x
joomla-framework/database#313

[teoberi]

The correction is not even in Joomla 5.2.1, I still have to manually modify the lines in the patch!

[richard67]

The correction is not even in Joomla 5.2.1, I still have to manually modify the lines in the patch!

@teoberi Confirmed. But you can be sure it will be included in the upcoming 5.2.2 which is scheduled for Tuesday, November 26. I've just checked the already prepared packages which are already in the internal testing phase. The reason why it was not in 5.2.1 is because 5.2.1 was just a quick security release to fix the file permissions issue for new installations, and besides that it was equal to 5.2.0.

@smng Unfortunately 4.4 is already in the security-only support phase and so might not receive any bug fixes but only security updates.

So currently when using 4.4 on PostgreSQL 16, you have an issue when going to the system information, and you cannot update to 5 without your workaround.

If we stick with this and not fix it in 4.4, we have at least to update our documentation about the system requirements and add a not about PostgreSQL >= 16 with a link to an FAQ page which explains your workaround.

I will bring it up in the CMS Maintenance Team so it gets discussed there and at least the necessary documentation will be made.