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, but being unable to upgrade even for security issues etc would be very bad news for us. From app.yml: - "templates/postgres.12.template.yml" Running ./launcher rebuild app: FAILED -------------------- Errno::ENOENT: No such file or directory @ rb_sysopen - /etc/postgresql/13/main/pg_hba.conf Location of failure: /pups/lib/pups/replace_command.rb:8:in `read' replace failed with the params {"filename"=>"/etc/postgresql/13/main/pg_hba.conf", "from"=>"/^host.*all.*all.*::1\\/128.*$/", "to"=>"host all all ::/0 md5"} 0ba8112e6efa1ac2dd75af8a1da8eea0937e7aefbca2df28b22d27e9608d1479 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem. Currently running version 2.8.0.beta4 75b0d6df93.

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”,

[תמונה] 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?

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:

דיון על postgres 12 שובר שדרוגים

תמיכה התקנה

Wingtip 26 באוגוסט,‏ 2021,‏ 7:03pm 5

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

נושא		תגובות	צפיות
Rebuild fails on db:migrate w/PG12 Self-hosting	18	2354	31 בדצמבר,‏ 2022
Upgrade failed: PostgreSQL version 13 ... not compatible with ... version 10.12 Self-hosting	6	1756	17 באפריל,‏ 2021
PostgreSQL 12 update Announcements	0	16079	12 במאי,‏ 2020
Old Postgres on Docker Image with two containers: web and data Self-hosting two-container	9	1865	18 בנובמבר,‏ 2020
Problem with upgrading the latest version Self-hosting	7	3174	22 ביוני,‏ 2020

דיון על postgres 12 שובר שדרוגים

נושאים קשורים