pg-event-proxy-example
temporal_tables
pg-event-proxy-example | temporal_tables | |
---|---|---|
1 | 6 | |
8 | 588 | |
- | 3.3% | |
10.0 | 4.9 | |
over 2 years ago | 5 months ago | |
PLpgSQL | PLpgSQL | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pg-event-proxy-example
-
All the ways to capture changes in Postgres
It exists [0] but does not seem to be that interesting to users
[0] https://github.com/subzerocloud/pg-event-proxy-example
temporal_tables
- PostgreSQL temporal_tables extension in PL/pgSQL
-
Versioning data in Postgres? Testing a Git like approach
It was reimplemented in pure SQL here https://github.com/nearform/temporal_tables for this purpose
-
All the ways to capture changes in Postgres
I enjoyed this blog. I think it provides a great succinct overview of various approaches native to Postgres.
For the "capture changes in an audit table" section, I've had good experiences at a previous company with the Temporal Tables pattern. Unlike other major RDBMS vendors, it's not built into Postgres itself, but there's a simple pattern [1] you can leverage with a SQL function.
This allows you to see a table's state as of a specific point in time. Some sample use cases:
- "What was this user's configuration on Aug 12?"
- "How many records were unprocessed at 11:55pm last night?"
- "Show me the diff on feature flags between now and a week ago"
[1]: https://github.com/nearform/temporal_tables
-
Show HN: I made a CMS that uses Git to store your data
One of these Postgres-based implementations of SQL:2011's temporal versioning features might get you close enough:
- https://github.com/nearform/temporal_tables
-
How to implement row changes history?
You don't really need to install an extension to use temporal tables, there is an alternative (https://github.com/nearform/temporal_tables) implemented purely as a plpgsql trigger so that it works everywhere.
-
Temporal Tables PostgreSQL Extension
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
If you're also limited by cloud services and the extensions limitations, this is a great solution.
What are some alternatives?
maxwell - Maxwell's daemon, a mysql-to-json kafka producer
temporal_tables - Temporal Tables PostgreSQL Extension
walex - Postgres change events (CDC) in Elixir
pgkit - Pgkit - Backup, PITR and recovery management made easy
connectors - Connectors for capturing data from external data sources
airbyte - The leading data integration platform for ETL / ELT data pipelines from APIs, databases & files to data warehouses, data lakes & data lakehouses. Both self-hosted and Cloud-hosted.
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
talk-transcripts - Transcripts of Clojure-related talks
wasmer.io - The Wasmer.io website