News for hackers. Stuff that matters.
Re:Migrating to Postgres by amazingamazing on Wednesday May 14, 2025 @07:47PM (#43990379)
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.

Re:Migrating to Postgres by sroussey on Wednesday May 14, 2025 @08:09PM (#43990509)
I typically go for 3rd normal form, and selectively denoralize where it has true performance value.
Re:Migrating to Postgres by spudlyo on Wednesday May 14, 2025 @09:15PM (#43990870)
“Normalize ’til it hurts, denormalize ’til it works.”
Re:Migrating to Postgres by rrr_oh_man on Thursday May 15, 2025 @12:36AM (#43991886)
Just saying this feels like it elevates you above 80% of people who work with databases.
Re:Migrating to Postgres by williamdclt on Thursday May 15, 2025 @05:29AM (#43993281)
> 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)