OpenLogReplicator
pg_ivm
| OpenLogReplicator | pg_ivm | |
|---|---|---|
| 2 | 21 | |
| 252 | 797 | |
| - | 5.0% | |
| 8.7 | 6.3 | |
| 5 days ago | about 2 months ago | |
| C++ | C | |
| GNU General Public License v3.0 only | 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.
OpenLogReplicator
- FLaNK AI-April 22, 2024
-
Features I'd Like in PostgreSQL
Good luck with that! Oracle have never made anything that they can't extract money from. In this case look to their attempts to kill logminer (which most CDC systems eg. Debezium use) and force you to pay for Goldengate hub/microservices/cloud.
Not tried it, but https://github.com/bersler/OpenLogReplicator
pg_ivm
- Postgres is eating the database world
-
What Is Incremental View Maintenance (IVM)?
FTA, because I don't like Jeopardy questions in headlines:
“Incremental View Maintenance (IVM) provides a method for keeping materialized views current by calculating and applying only the incremental changes, as opposed to the complete recomputation of contents performed by the REFRESH MATERIALIZED VIEW command.”
Article shows using the pg_ivm Postgres extension available here: https://github.com/sraoss/pg_ivm
- Pg_ivm: Incremental View Maintenance as a Postgres Extension
- Anyone have experience with incremental materialized views in postgres?
- Incremental View Maintenance for PostgreSQL
-
a temporary-ish table vs materialize view?
There is an extension that provides some limited incremental MVIEW refresh: https://github.com/sraoss/pg_ivm
- Features I'd Like in PostgreSQL
- IVM (Incremental View Maintenance) Implementation as a PostgreSQL Extension
-
Materialized View: SQL Queries on Steroids
There’s awesome work being done on incremental view maintenance in postgres:
https://github.com/sraoss/pg_ivm
-
Should I replace all db select query REST APIs with a single generic router ?
It makes sense to perform managed denormalization - use a materialized view or automatically refresh a table or foreign server (via FDW) using common triggers (like pg_ivm does). And it's fine to add a TTL to it and use as a read store... update on user login and make a partial index just for that. And that's how you could get CQRS...
What are some alternatives?
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
prawn-stack - A pageview counter using the AWS free tier, Postgres, Node and React
pg_hint_plan - Extension adding support for optimizer hints in PostgreSQL
materialize - The data warehouse for operational workloads.
ora2pg - Ora2Pg is a free tool used to migrate an Oracle database to a PostgreSQL compatible schema. It connects your Oracle database, scan it automatically and extracts its structure or data, it then generates SQL scripts that you can load into PostgreSQL.
gql-sql-pgq-pointers
contour - Contour is a Kubernetes ingress controller using Envoy proxy.
Hashids.java - Hashids algorithm v1.0.0 implementation in Java
pg_jsonschema - PostgreSQL extension providing JSON Schema validation
rum - RUM access method - inverted index with additional information in posting lists
risingwave - SQL stream processing, analytics, and management. We decouple storage and compute to offer instant failover, dynamic scaling, speedy bootstrapping, and efficient joins.