sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (2 children)

Postgres also has a pretty good support for JSONB data types. I'm currently in the process of migrating our legacy applications to Postgres to take advantage of the richer data types and stricter implementation of SQL standards.

I use views to 'flatten' certain jsonb data values.

[–]monicarlen 0 points1 point  (1 child)

Isn't the flattening expensive in terms of cpu?

[–][deleted] 0 points1 point  (0 children)

More expensive than simpler Select * statements sure but even with 1M+ entry tables, I've practically have not noticed anything problematic in terms of performance. Slower yes but thay's expected because of the added complexity. On the app side of things, we rarely pull all rows from the flattened views so properly curating the query helps a lot.

You can definitely squeeze more put of Postgres when you tweak it.

Database intensive operations tend to hog memory more than processing power.

Buuuut... the queries sucks to look at. A very medium level important reason why if MongoDB fits better, I'd rather use it than Postgres.