> If you don't want to pay the cost of updating the full JSON value, that's what columns are for. You pay the full cost for writing the entire new row in Postg

> If you don't want to pay the cost of updating the full JSON value, that's what columns are for. You pay the full cost for writing the entire new row in PostgreSQL if only a single column changes. There’s some saving for indexes, but the row data is always written in full for the new row even if just one column changes. Now that’s no reason not to use actual columns. The value of a well defined schema is knowing the types and constraints of your data.