v3.5.2 → v3.5.2 v3.6.0.beta2 → v3.6.0.beta2 This thread got me to this point: Upgrade failed. Database stopped. (multisite install) I now have database access issues: 2025-11-02 17:13:51.212 UTC [1975] postgres@c_discourse LOG: provided user name (postgres) and auth…

I used apt to install the new extention and got it to work. Geez. Now to do proper backups and update to Postges 15. But, not tonight. :wink: My history seemed to get wiped so I can’t tell you exactly how I did that but beware. It requires postgres 13 and will try and reinstall that. I…

Database access issues after upgrade v3.5.2 -> v3.6.0.beta2

Support

tobiaseigen (Tobias Eigen) November 3, 2025, 4:02pm 3

Your post is super hard to read, so I have unlisted it Please fix the formatting and I can list it again.

2 Likes

Topic		Replies	Views
Upgrade failed. Database stopped. (multisite install) Installation	19	198	November 3, 2025
Unable to upgrade discourse with separate data container Installation	4	2254	November 7, 2016
Failing update Installation	35	327	September 25, 2025
Failed to upgrade to v2.9.0beta3 Installation	9	1036	May 22, 2022
Database files are incompatible with server (updating inside Linode) Support	14	352	February 6, 2025

Database access issues after upgrade v3.5.2 -> v3.6.0.beta2

Related topics