In Postgres land, I think most businesses work around temporal tables with audit tables using triggers to dump jsonb or hstore. I wrote up how I used table-inhe

In Postgres land, I think most businesses work around temporal tables with audit tables using triggers to dump jsonb or hstore. I wrote up how I used table-inheritance here [1]. I agree with your point. Postgres is starting to stick out compared to alternatives: - MS SQL supports uni-temporal tables using system time. - Snowflake has time travel which acts like temporal tables but with a limited retention window. Seems more like a restore mechanism. - MariaDB has system-versioned tables (doesn't look like it's in MySQL). - Cockroach DB has uni-temporal support with system time but limited to the garbage collection period. The docs indicate you don't want a long garbage collection period since all versions are stored in a single range. - Oracle seems to have the best temporal support with their flashback tech. But it's hard to read between the lines to figure out what it actually does. [1]: https://news.ycombinator.com/item?id=29010446 https://news.ycombinator.com/item?id=29010446