pg_ivm
ora2pg
Our great sponsors
| pg_ivm | ora2pg | |
|---|---|---|
| 19 | 3 | |
| 774 | 959 | |
| 9.9% | - | |
| 6.3 | 9.0 | |
| about 1 month ago | 19 days ago | |
| C | Perl | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
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_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...
ora2pg
-
Oracle Auto indexes missing after ora2pg migration? Look at CONSTRAINT_INDEX
It seems that Oracle customers started using the Auto Index feature. I can see that when they migrate to YugabyteDB. YugabyteDB Voyager is a tool to ease the migration of schema and data. As YugabyteDB is PostgreSQL compatible, ora2pg is used when the source is Oracle. It extracts the schema and data. Some customers moving from Oracle ATP managed service (Autonomous Transaction Processing) reported that a few indexes were not extracted: the ones that have been created automatically by the Automatic Indexing feature of Oracle 19c.
-
Features I'd Like in PostgreSQL
Have you heard of "ora2pg"? It works for both MySQL and Oracle:
https://github.com/darold/ora2pg
https://ora2pg.darold.net/
- Using Ora2Pg to Migrate Data from Oracle to openGauss
What are some alternatives?
prawn-stack - A pageview counter using the AWS free tier, Postgres, Node and React
pg_plan_guarantee - Postgres Query Optimizer Extension that guarantees your desired plan will not change
materialize - The data warehouse for operational workloads.
rum - RUM access method - inverted index with additional information in posting lists
pg_hint_plan - Extension adding support for optimizer hints in PostgreSQL
OpenLogReplicator - Open Source Oracle database CDC
contour - Contour is a Kubernetes ingress controller using Envoy proxy.
gql-sql-pgq-pointers
pg_jsonschema - PostgreSQL extension providing JSON Schema validation
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes