Hettie

4 ms·

1. 1.▲
   by Hettie 6y ago

   Check out our framework for bitemporlity: https://github.com/scalegenius/pg_bitemporal We use it in production for 5 years. I am ready to answer any performance/indexing and other questions
2. 2.▲
   by Hettie 7y ago

   I am shamelessly promoting it, because we have no bandwith to make it to the extension, and for the past almost three years we've been promised by several people/organizations to create an extension or even to incorporate it into
3. 3.▲
   by Hettie 7y ago

   YES! And moreover, I am actively using it in production, we've added lots of new functions, and made it PG 10 comatiable
4. 4.▲
   by Hettie 7y ago

   From my humble experience, performance of such views will be suboptimal. When we started our implementation of AVF (Johnson and Weis), we just decided to believe the authors, that people only "think" that storing all of the histor
5. 5.▲
   by Hettie 7y ago

   https://github.com/scalegenius/pg_bitemporal
6. 6.▲
   by Hettie 7y ago

   This one requires to create historical tables for each "regular" table, like in SQL 2011, in AVF you keep everything in one table, this feature provides a unique level of querying flexibility for temporal queries.
7. 7.▲
   by Hettie 7y ago

   We've implemented a full Asserted Versioning Framework (Johnson and Weis) for Postgres, and use it in production. Using it for about 18 months for both OLPT and OLAP. works beautifully :)