-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix postgresql 13 recovery #4521
Conversation
2ddcaad
to
00f7a0a
Compare
Testing the image build from this branch: https://github.com/raspiblitz/raspiblitz/actions/runs/8567463654 still not looking good when recovering on an RPi5 loaded with a pg13 on disk
|
so this is still a showstopper for v1.11.0 - correct? |
yes it seems that's still the case. Will need to clear all clusters before recovering I think, but will need to test more. |
Set to test the new image from this branch: |
d4c7123
to
f352b1d
Compare
recovered from pg13 was ok on the last one so looking good. next image with a small tweak now: https://github.com/raspiblitz/raspiblitz/actions/runs/8574541229 manual testing is still needed as cannot reproduce the process fully in bats |
f352b1d
to
4e82d8c
Compare
Looking good now, merging and cherry-pick to v1.11
|
* postgres: add comments, backup and remove unused databases * bats: remove output, use --verbose-run locally * always drop empty pg 15 cluster * check cluster correctly, fix port after upgrade * always restart postgresql.service to fix port
cherry-picked to v1.11 |
* postgres: add comments, backup and remove unused databases * bats: remove output, use --verbose-run locally * always drop empty pg 15 cluster * check cluster correctly, fix port after upgrade * always restart postgresql.service to fix port
Related: #4508 and #4496