3 ms·
I don't disagree with your point, but over normalization and joining everywhere also isn't necessarily the answer, even with an index. there's no easy answer to
by amazingamazing 1y ago
I don't disagree with your point, but over normalization and joining everywhere also isn't necessarily the answer, even with an index. there's no easy answer to this, really depends on the performance characteristics the critical user journeys need.
with a little pain, if I had to pick an extreme, I'd pick extreme normalization with materialized views that are queried (e.g. no joins), rather than joining all of the time.
- sroussey 1y agoI typically go for 3rd normal form, and selectively denoralize where it has true performance value.
- spudlyo 1y ago“Normalize ’til it hurts, denormalize ’til it works.”
- rrr_oh_man 1y agoJust saying this feels like it elevates you above 80% of people who work with databases.
- williamdclt 1y ago> materialized views how though? Postgres doesn't support auto-refreshing materialized views when the underlying data changes (with good reasons, it's a really hard problem)