![]() ![]() launcher stop app #(or both web_only and data if that is your case) If you are in a constrained space environment without any way to get more space you can try the following. YOU MUST BACKUP THE POSTGRES_DATA BEFORE TRYING THIS 18:33:33.479 UTC LOG: database system is shut downĭoing a manual update / space constrained environments ![]() 18:33:33.464 UTC LOG: worker process: logical replication launcher (PID 52) exited with exit code 1 ![]() Running a tail -f shared/data/log/var-log/postgres/current should give you the following log if it was clean: 18:33:33.457 UTC LOG: received smart shutdown request Nowadays, we have background jobs running queries spanning several minutes, so shutting down the web container will help the data container be shutdown safely./launcher stop web_onlyīefore issuing the first rebuild to the data container, you can tail the PostgreSQL log to see if it was shutdown properly. If you are running a setup with a dedicated data container based in the sample supplied in our discourse_docker repository, you want to be sure you are shutting down PostgreSQL in a safe and clean way. That means everything went well in the upgrade! You just need to issue a new rebuild to get your site back and running. To complete the upgrade, rebuild again using: Old 12 database is stored at /shared/postgres_data_old On you next rebuild, you will see this message at the end:. Updating Official Install Guide (single container) If you had held back the upgrade previously, change the PostgreSQL template in app.yml from templates/postgres.10.template.yml to templates/.Īs with any upgrade, it is strongly advised to take a backup before doing anything. Note that if you held back from upgrading when the PostgreSQL 12 update happened back in May, you can skip that upgrade and go straight to PostgreSQL 13. Any site admins rebuilding Discourse from the command line will be upgraded to PostgreSQL 13 from the previous PostgreSQL 12. We’ve just landed changes to upgrade our Docker image to PostgreSQL 13. WARNING! If your database is very large, you will need a lot of extra disk space (2x database size) and should be very careful with this upgrade! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |