alt Hacker NewsOoh fantastic. I’ve been using date ranges plus GIST indexes for like a decade to do this. It’s really nice. But the lack of foreign keys can be painful. I’ve resorted to stored procedures for crates and updates to ensure everything is done right and enforced.
This is WAY easier.
The FK piece is what I'm most excited about. PRIMARY KEY WITHOUT OVERLAPS plus FOREIGN KEY ... PERIOD means a child row's range is enforced to stay inside an actual parent version, no triggers or sprocs needed. Not free (GiST lookups add up on hot tables), but for slowly changing dimensions it kills a whole class of footgun.