We recently had a funny problem. Our service ran fine, but a postgres upgrade failed because some pg internals were broken (broken ref ids). Dumping the DB also failed for the same error. Reading and writing was still fine, though. So we restored backup after backup... no dice. They all had the same issue: it was working for the service but we couldn't perform any maintenance. Ultimately we had to "manually" dump the data of the service and replay it into a fresh db. That took quite long. But that was interesting, since even the verification of the backups didn't help us notice that kind of corruption.
- Posts
- 2
- Comments
- 408
- Joined
- 2 yr. ago
- Posts
- 2
- Comments
- 408
- Joined
- 2 yr. ago
Which is completely reasonable. Insanity is trying the same thing over and over and expecting different outcomes.
It's not like they tried nothing and are all out of ideas; they tried a lot and nothing stuck so far.