Various issues upgrading 1.2.0 to 1.3.1 #578
-
Hi, So it seems to be working right now, but I don't really trust that's it's fully working given all the issues I've had. First thing I did was to backup the database like so:
I then updated the Docker configurations according to these instructions. I shut everything down and tried restoring the database. Didn't work due to postgres container missing. I guess I wasn't supposed to shut it all down. Had lots of "Waiting on DB" issues. Fast forward a bit, I found this page on upgrading PostgreSQL. The 1.3.0 release notes didn't say anything about needing to wipe the database, so I'm not sure if that was necessary. Once I did that and tried restoring the database again I got countless errors regarding missing relations, indices, tables and sequences, and the same errors when I started the container. It did come up though, and at a quick glance my data seems to be there, but I don't know whether I should be concerned. I've never had any issues updating before. I'm also getting this, which I thought was the cause of the "Waiting for DB" errors, but that seems to be there even now that it's working, and might have been there all this time:
Possibly irrelevant, but there's slightly conflicting (or not) documentation on how to perform an update on these pages: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Ok, I figured the errors were about altering the database, but since it was empty that was to be expected. I also realised I had issues with disk space, which was the cause of the postgres not coming up the first time around. |
Beta Was this translation helpful? Give feedback.
Ok, I figured the errors were about altering the database, but since it was empty that was to be expected. I also realised I had issues with disk space, which was the cause of the postgres not coming up the first time around.