As far as I can tell, alternate between updating, checking formatting for the tables, making sure everything is similar between source and host, and watching it fail multiple times, and that might or might not work without some minor database edits.
I have successfully migrated 2 of 3 sites, and am forced to use less than one hour a day on it for sanity. I have begun talking to the clients about the issues this could cause in the future with any similar situation. shrug
Thanks, Gerhard. I don’t know if you care now, but I’m also having trouble with a site that’s using PG 11 with GCP. It might be worth checking on that as it might affect the future move to PG12 that I understand should happen later this fall.
I just upgraded two instances that share an S3 backup bucket. I ran a backup on one and tried to restore on the other and get
Both sites are 2.4.0.beta6 (8fc0cc9aaa). The backups (but not uploads) are on S3.
discourse restore returns
Starting restore: wonderful-community-2019-10-10-184822-v20191007140446.tar.gz
'system' has started the restore!
Marking restore as running...
Making sure /var/www/discourse/tmp/restores/default/2019-10-10-211121 exists...
Downloading archive to tmp directory...
Unzipping archive, this may take a while...
/var/www/discourse/lib/compression/gzip.rb:49:in `block in extract_file'
Of course, and I think that site will be satisfied with direct database backups on GCP anyway, but at some point Sam said that he was running PG 11 on his dev site and that he’d be interested to know of problems with PG11.
What if you try to remove any s3 dependency and copy the backup file to local first?
@pfaffman it might be good to know that the two (or three) restore issues you have posted in this topic are not occurences of the bug that this topic was originally about (the PG::UndefinedColumn: ERROR issue). You might consider opening new topics for these since they are clearly different issues.