@GigaByte4711 You have my emotional support.
@GigaByte4711 Do you have the error log from the failed migration? What versions were you coming from / going to?
I'm trying to move off docker, and to a normal instance.
The database won't dump, due to an error in the statuses table, so I can't migrate the table.
@GigaByte4711 Have you managed to fix your issue? It seems like it's postgres related, the only thing I could find was this post: https://stackoverflow.com/questions/51980812/multixactid-has-not-been-created-yet-apparent-wraparound-error-in-postgres
I've never experienced it myself, so I don't have any specific tips, but check out the postgres page on data corruption before taking any action: https://wiki.postgresql.org/wiki/Corruption
Afraid not. I read that same issue, and the corruption guide. I've got a FS-level backup, but ad I'm not really proficient in postgresql, I've not been able to make much headway. I'm off work this week, so I'll probably end up doing my troubleshooting on IRC then.
Whitespashe works fine on the damaged db, but I just can't make DB backups. I've been relying on VM snapshots and nightly lun snapshots for my backup options.
@GigaByte4711 If you have a chance to update the minor on your postgres image it might be a good idea, assuming it's a postgres bug it could already solve the issue for you (if you are in 9.6.x to upgrade to 9.6.12, or if you are in 10.x to update to 10.7)
When I had an index corruption regenerating the index solved it, though I had to manually erase some dup entries that were created because the index was a unique.
U could try regenerating the indexes to check if it changes something
I'll try the reindex in a second, see if that helps. And I'll take a look at the minor version options.
I'm pretty sure the corruption came as part of a power outage and disk failure I had early on, but as the database came straight back up and started working, I must have overlooked it.
Image update worked, now running the latest alpine docker image for 9.6.
Unfortunately the reindex errors at the same point with the original error. 😥
@GigaByte4711 oh noes :(
I found this on medium, seems similar and there's a solution at the end : https://medium.com/in-the-weeds/postgresql-multixactid-error-in-vacuum-106af8fbf022
I tried to follow along with that, but attempting to delete the row returns 'DELETE 0'
Unfortunately, it doesn't say why it didn't delete the row. :(
@GigaByte4711 Shit :T
You tried vacuuming too?
Posting again because of snapshot rollback:
Yeah, vacuum fires the same error as the other attempts. This week is gonna be filled with frantic IRC-ing trying to get this sorted. The only other thing I can think of is truncating the statuses table, but as it's linked to other tables, they get truncated too.
I effectively nuke the posting history of my instance, and I'm not sure that's what I want.
@GigaByte4711 Can you paste on a gist or something like that the commands and responses you got from trying to delete that bad id?
Sure, gimme a bit, gonna switch to my laptop, rather than ssh from my phone.