pg_ivm
pg_plan_guarantee
| pg_ivm | pg_plan_guarantee | |
|---|---|---|
| 19 | 4 | |
| 774 | 83 | |
| 9.9% | - | |
| 6.3 | 0.0 | |
| about 1 month ago | almost 2 years ago | |
| C | C | |
| GNU General Public License v3.0 or later | PostgreSQL License |
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...
pg_plan_guarantee
-
Features I'd Like in PostgreSQL
For 4) I've heard there's this available https://github.com/DrPostgres/pg_plan_guarantee
-
Demystifying Database Performance for Developers
Shameless plug(s). To address both the problems you described, I have developed the following Postgres extensions.
Index Adviser can be used to automatically analyze your workload, and it will suggest the indexes that might help your queries perform better.
Postgres Plan Guarantee (under development) helps you generate+freeze a plan, and ensure that the Query Optimizer will never pick a different plan for your query.
Postgres Index Advisor: https://github.com/DrPostgres/pg_adviser
Postgres Plan Guarantee: https://github.com/DrPostgres/pg_plan_guarantee
- New extension: pg_plan_guarantee – Guarantee that your (query) plans will never change
- Show HN: Pg_plan_guarantee – Guarantee that your (query) plans will never change
What are some alternatives?
prawn-stack - A pageview counter using the AWS free tier, Postgres, Node and React
plpgsql_check - plpgsql_check is a linter tool (does source code static analyze) for the PostgreSQL language plpgsql (the native language for PostgreSQL store procedures).
materialize - The data warehouse for operational workloads.
pg_hint_plan - Extension adding support for optimizer hints in PostgreSQL
pg_adviser - Postgres' index adviser
contour - Contour is a Kubernetes ingress controller using Envoy proxy.
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.
pg_jsonschema - PostgreSQL extension providing JSON Schema validation
sqlite-gui - Lightweight SQLite editor for Windows
OpenLogReplicator - Open Source Oracle database CDC