> Recently someone started appending to a json field type over and over in our production database. And then on some queries, postgres crashed due to lack of me

> Recently someone started appending to a json field type over and over in our production database. And then on some queries, postgres crashed due to lack of memory. The fix was to remove the field and code that constantly appended to it, and do something else. So your choices are doing something manifestly non-optimal in the database in violation of best practices or not use the database for non-trivial business logic? Sounds like a false dichotomy to me. Maybe just find a better solution? I mean, if someone writes an O(n^3) algorithm in Python, is the solution to use a better strategy or to swear off Python for anything non-trivial?