5 ms·
I was part of a team at NearForm using this for a project on an EC2 instance. In order to move to AWS RDS we had to recreate the functionality of temporal_table
by Codesleuth 5y ago
I was part of a team at NearForm using this for a project on an EC2 instance. In order to move to AWS RDS we had to recreate the functionality of temporal_tables as a PostgreSQL function, rather than extension.
When we switched, we found that although there were minor bugs, we didn't have any noticeable loss of performance and we have used it ever since for many projects.
https://github.com/nearform/temporal_tables https://github.com/nearform/temporal_tables
If you're also limited by cloud services and the extensions limitations, this is a great solution.
- take-five 5y agoWe also started with "temporal_tables" C-extension, and also had to switch to NearForm's version written in PL/pgsql to be able to migrate our database to RDS. Didn't notice any performance drop. It also much easier to install (just run an SQL-script, no need to restart the DB) and it works everywhere, on all PostgreSQL versions. Great piece of work!
- antman 5y agoI see you have a “nochecks” version, what would be its use case?
- luto 5y agoIt says right there in the readme: performance. > This version is 2x faster than the normal one, but more dangerous and prone to errors.