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…

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

Sadly I went to great lengths to make is as comprehensible/coherent as I could. I know what I mean. :wink: EDIT: OK, got it. The other forum I use is a tad different. I use triple tics on the line before and after the block. Now I see what is going on. This one the first set of tics inserts …

You can toggle to the markdown editor if you need to do lots of markdown things in your post. Your database password issues are strange. Have you considered moving to a new server? That might be quicker and easier than battling with this issue.

Did you follow these instructions? (It doesn’t seem like it?) [imagen] Multisite configuration with Docker hooks: after_postgres: - exec: sudo -u postgres createdb b_discourse || exit 0 - exec: stdin: | grant all privileges on database b_discourse to discourse; …

[imagen] pfaffman: Did you follow these instructions? (It doesn’t seem like it?) I wondered why I named my databases b_discourse and c_discourse. Now I know why. :wink: ## Plugins go here ## see https://meta.discourse.org/t/19157 for details hooks: after_postgres: - exec: sudo -u pos…

Well, good news bad news. :frowning: Now we want :frowning: 2025-11-07 18:05:41.555 UTC [4724] discourse@b_discourse ERROR: must be owner of extension vector 2025-11-07 18:05:41.555 UTC [4724] discourse@b_discourse STATEMENT: ALTER EXTENSION vector UPDATE TO '0.8.0'; 2025-11-07 18:05:41.752 UTC …

Is there a way to get ./launcher to connect as the user postgres? That seems like it would cure all my upgrade issues here. b_discourse=# select e.extname, u.usename from pg_extension e join pg_user u on e.extowner = u.usesysid; extname | usename ----------+-------…

Problemas de acceso a la base de datos tras la actualización v3.5.2 -> v3.6.0.beta2

Soporte

tobiaseigen (Tobias Eigen) 3 Noviembre, 2025 16:02 3

Tu publicación es muy difícil de leer, así que la he despublicado. Por favor, arregla el formato y podré volver a publicarla.

Tema		Respuestas	Vistas
Upgrade failed. Database stopped. (multisite install) Self-hosting	20	364	3 Diciembre 2025
Unable to upgrade discourse with separate data container Self-hosting	4	2275	7 Noviembre 2016
Failing update Self-hosting	35	586	25 Septiembre 2025
Failed to upgrade to v2.9.0beta3 Self-hosting	9	1079	22 Mayo 2022
Rebuild fails: Data directory /shared/postgres_data must not be owned by root Self-hosting	5	535	5 Febrero 2025

Problemas de acceso a la base de datos tras la actualización v3.5.2 -> v3.6.0.beta2

Temas relacionados