We’re running postgres v12 as the v13 upgrade requires too much disk space. It looks like compatibility with v12 may have been broken? Is this deliberate? If so it means we can never upgrade Discourse again. Running ./launcher start app got us back online so it isn’t a production issue right now, b…

Fixed in https://github.com/discourse/discourse_docker/pull/566 Can you please try rebuilding again @Wingtip ? That said, we don’t run PG12 anymore, so we may introduce some SQL syntax exclusive to PG13+ anytime in core, so it would be a good idea to schedule the upgrade someday.

its looking for postgress 13 and not 12. {“filename”=>“/etc/postgresql/13/main/pg_hba.conf”,

[image] Wingtip: We’re running postgres v12 as the v13 upgrade requires too much disk space. Why don’t you back-up, create a totally fresh discourse instance (which should default postgres 13), restore back-up and remap the server in DNS?

That would work, yes. Desperately trying not to have to do that.

Might seem scary, but you’d have enough safeguards there, you can always bring the old server back online.

It’s less scary than annoying work I’d like to avoid, combined with telling my forum they’re going to lose a day or two of posts. Would like the Discourse guys to say “Of course we still work on PG12, that’s just a bug, we’ll get that fixed up” ideally.

I can’t see why that’s necessary. Prepare new server on subdomain? Enter read-only mode on existing server, create back-up Pull in back-up on new server Remap DNS Rebuild new server with primary discourse subdomain. This process could take 30 mins?

Ah! A nice problem to have! :slight_smile:

I suppose, it’s not like I’m paid! :wink:

Discourse sur postgres 12 perturbe les mises à niveau

Soutien Installation

merefield (Robert) Août 26, 2021, 7:02 4

Pourquoi ne pas faire une sauvegarde, créer une instance Discourse complètement nouvelle (qui devrait utiliser Postgres 13 par défaut), restaurer la sauvegarde et mettre à jour l’enregistrement DNS du serveur ?

Sujet		Réponses	Vues
Rebuild fails on db:migrate w/PG12 Self-hosting	18	2275	Décembre 31, 2022
Upgrade failed: PostgreSQL version 13 ... not compatible with ... version 10.12 Self-hosting	6	1715	Avril 17, 2021
PostgreSQL 12 update Announcements	0	15950	Mai 12, 2020
Old Postgres on Docker Image with two containers: web and data Self-hosting two-container	9	1785	Novembre 18, 2020
Problem with upgrading the latest version Self-hosting	7	3091	Juin 22, 2020

Discourse sur postgres 12 perturbe les mises à niveau

Sujets connexes