Where are you getting the idea that this was a dumb rash decision? It sounds like they upgraded the database instance without proper QA in the first place and t

Where are you getting the idea that this was a dumb rash decision? It sounds like they upgraded the database instance without proper QA in the first place and that this created a lot of issues. OP didn't specify if this was their decision or not, but even if it was there might be some good reasons for it and many of those reasons point to further organisation incompetence. The only rash decision OP made (from the information available) was to disable the feature in production to at least get the appearance of everything working, which was the status quo. This is shooting the messenger, the product was silently failing for god knows how long and your blaming the person that forced the organisation to acknowledge those failures and their own personal incompetence. And they did this in a way that only had an immediate impact on non-production systems. I get the impressions you can't work well with others, because it requires a good dose of humility and the ability to acknowledge problems. Sweeping those problems under the carpet to bite people in mysterious ways at odd times is someone that's difficult to work with.