- UPDATE POSTGRESQL INSTALL
- UPDATE POSTGRESQL UPDATE
- UPDATE POSTGRESQL MANUAL
- UPDATE POSTGRESQL UPGRADE
UPDATE POSTGRESQL UPGRADE
When this happens your upgrade logs will contain mv: cannot move '/shared/postgres_data' to '/shared/postgres_data_old/postgres_data': Directory not empty Every rebuild does the upgrade again aka upgrade loop Ensure that the env: section of you app.yml file has the 3 lines: LC_ALL: en_US.UTF-8Ĭhanging en_US.UTF-8 to your locale. It was reported that you need 3 variables for it to succeed. This errors happens if you are using non-default locales for your database. lc_collate values for database “postgres” do not match If the logs look like above, you can now try to upgrade again using. 18:33:33.457 UTC LOG: received smart shutdown request After that tail the logs to see if it was a clean one: tail -f shared/data/log/var-log/postgres/current If you get a upgrade failed with the above message, you can try a simpler approach to get it back into a better state. If you have a separate data container, you’ll need to remove the backup copy like this: rm -fr /var/discourse/shared/data/postgres_data_old/įAQ The source cluster was not shut down cleanly
Or this one-line version of the above: /var/discourse/launcher run app "echo 'vacuum verbose analyze ' | su postgres -c 'psql discourse'"įor a standard install, you can delete the old data in PG10 format with the following command: cd /var/discourse
You can generate those using: cd /var/discourse
UPDATE POSTGRESQL UPDATE
Post update optional tasks Optimizing PostgreSQL statisticsĪfter the update, the new PostgreSQL won’t have table statistics on hand. This is not recommended, as some site admins will forget to revert the change afterwards. If you need to postpone the update during your next rebuild, you can swap the PostgreSQL template on your app.yml file by changing "templates/" to "templates/postgres.10.template.yml". On my tests this procedure requires less than 1x your current database size in free space. launcher rebuild app #(or first data and then web_only if that is your case) Mv /var/discourse/shared/standalone/postgres_data_new /var/discourse/shared/standalone/postgres_data Mv /var/discourse/shared/standalone/postgres_data /var/discourse/shared/standalone/postgres_data_old v /var/discourse/shared/standalone/postgres_data_new:/var/lib/postgresql/12/data \ v /var/discourse/shared/standalone/postgres_data:/var/lib/postgresql/10/data \ Mkdir -p /var/discourse/shared/standalone/postgres_data_new 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
UPDATE POSTGRESQL MANUAL
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: On you next rebuild, you will see this message at the end: Upgrade Complete
UPDATE POSTGRESQL INSTALL
Updating Official Install Guide (single container) PostgreSQL 12 brings lots of improvements that will be automatically leveraged by Discourse. We are running this new version for a while on Meta, and everything is working fine. Any site admins rebuilding Discourse from the command line will be upgraded to PostgreSQL 12 from the old PostgreSQL 10.
We just landed the long waited PostgreSQL major version upgrade. 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 kommentar(er)
