Sure, I can appreciate that native support for a feature like this is nice. As I understand it, most implementations (including another one for bitemporality[1

Sure, I can appreciate that native support for a feature like this is nice. As I understand it, most implementations (including another one for bitemporality[1]) involve either audit tables, as you mention, and/or additional support columns. It's as if the "now" representation is simply a narrowed view within the full set of underlying, (bi)temporal data. That said, PostgreSQL encodes and has battle-tested decades of database functionality, including a surrounding ecosystem, so I'd be a little wary of switching technology even if it does solve one individual problem thoroughly. Everything has to start somewhere, though. [1] - https://github.com/scalegenius/pg_bitemporal https://github.com/scalegenius/pg_bitemporal