postgres 的升级失败

Falco · 2020 年9 月 25 日 20:19

Visiting that URL, there is a FAQ entry for it:

If you get a upgrade failed with the above message, you can try a simpler approach to get it back into a better state.

Restart the old container with ./launcher start app . Wait a few minutes until it is back up.

Now shut it down again with ./launcher stop app . After that tail the logs to see if it was a clean one:
tail -f shared/data/log/var-log/postgres/current
2020-05-13 18:33:33.457 UTC [36] LOG:  received smart shutdown request
2020-05-13 18:33:33.464 UTC [36] LOG:  worker process: logical replication launcher (PID 52) exited with exit code 1
2020-05-13 18:33:33.465 UTC [47] LOG:  shutting down
2020-05-13 18:33:33.479 UTC [36] LOG:  database system is shut down
If the logs look like above, you can now try to upgrade again using ./launcher rebuild app .

话题		回复	浏览量
Update failed (postgresql) Self-hosting	8	3844	2020 年6 月 3 日
Postgres upgrade success loop due to prior postgres 8 to 10 migration Self-hosting	4	1177	2020 年6 月 25 日
Site Won't Start After Update Self-hosting	7	1090	2018 年7 月 30 日
Cannot rebuild app because UPGRADE OF POSTGRES FAILED Self-hosting	8	226	2025 年3 月 14 日
Manual upgrade failure due to postgres error Self-hosting	1	453	2020 年10 月 28 日

postgres 的升级失败

相关话题