How dangerous is the use of PostgreSQL-Vers 18.2 with nextcloud-32.0.6?

[adelaar]

I have a running productive NC-Server (no AIO, no SNAP) Version 31.0.14 on Debian 12 and want to replace it with NC-Server (no AIO, no SNAP) Version 32.0.6 on Debian 13.

At the Debian 13 Server i do now run PostgreSQL 18.2, php8.4 and nginx, The problem is, PostgreSQL 18.2 will be supported not at Version 32 but the support will start on 33. On the other hand NC Version 33.0.0 seems to be not free of problems. So i do not want to install Version 33.0.0.

So the question is how dangerous is it to go further with switching a productive Server from Debian 12 to 13 with PostgreSQL 18.2 and Version 32.0.6?

View also:

As you can see, there is for some reason also no Update offered from 32.0.6 to 33.0.0.

[jtr]

@adelaar

So the question is how dangerous is it to go further with switching a productive Server from Debian 12 to 13 with PostgreSQL 18.2 and Version 32.0.6?

No one can answer with certainty since the Nextcloud v32 branch was/is not tested against PostgreSQL 18.

While tempted to say “it’ll probably be fine” (and it probably is) I would not do it in a production environment. Database incompatibilities do arise and you’d be unlikely to find a solution within v32 if that happens. Yeah, you might think “well I’ll just update to v33 if/when that happens” – well, that assumes: (a) the db matter didn’t cause data loss/corruption and it caught early enough to return to a recent backup (b) and you’re comfortable moving to v33 in an unplanned manner suddenly.

Individual experiences (“Hey it worked for me!”) may be comforting, but they aren’t apples to apples: Nextcloud deployments vary significantly (features used, apps installed, use cases, etc.)

Note you aren’t stuck. You have two paths (other than doing nothing):

• Use PostgreSQL’s own Debian Apt Repository (14+ available): PostgreSQL: Linux downloads (Debian)
• Use a Docker container or VM or separate host for the db

[adelaar]

@jtr

You have two paths (other than doing nothing

I have even more. I have done a full backup of the servers .qcow2 before i started to install NC-Server and it’s config. I use the repository of postgresql.org. This contains also postgresql-17.

Best option i see is to restore the new NC-servers .qcow2 and install postgresql-17 from repository of postgresql.org. This way i can use postgresql-17 instead of -18. So i just have to do the configs once again i have done since the Backup.

I am just annoyed with myself for not checking the issue with postgresql-18 beforehand.