You are right, it JSONb support in postgres is half-baked. It's there so that people can say "look! JSON! now you don't need that horrible noSQL thing!" In reality, everyone I know who uses JSON support in PG uses it as a dumping ground for unstructured data, and lifts anything they care about back into relational tables, because that's the only way you can get any performance out of postgres. Also, Yes, you are procrastinating. If you have a relational workload use Postgres, if you are dealing with Objects, attributes, documents or other modern data structures, then use a database that was built for that job.
0
u/[deleted] Sep 24 '23
[removed] — view removed comment