IVM Development Group is pleased to announce the release of [pg_ivm 1.15](
https://github.com/sraoss/pg_ivm/releases/tag/v1.14 ).
Changes since the v1.14 release include:
## What's Changed
### New features
* Add IMMV metadata restore support for pg_dump and pg_upgrade (Yugo Nagata)
After restoring a database from pg_dump or upgrading PostgreSQL using
pg_upgrade,
IMMVs no longer need to be dropped and recreated manually. The new
pg_ivm_dump_metadata
utility and restore_immv() function restore the metadata required by
pg_ivm, allowing incremental
maintenance to continue without recreating the IMMVs.
### Bug fixes
* Fix incorrect maintenance when the same table is modified multiple times by
triggers (Yugo Nagata)
Previously, if a table was modified multiple times by user-defined or RI
triggers,
incremental maintenance could produce inconsistent results or lead to
duplicate key violations.
* Fix segfault during outer-join views maintenance (Yugo Nagata)
This bug was introduced in v1.14.
### About pg_ivm
pg_ivm is an extension module that provides Incremental View Maintenance
(IVM) feature.
Incremental View Maintenance (IVM) is a way to make materialized views
up-to-date in
which only incremental changes are computed and applied on views rather
than recomputing.
pg_ivm provides a kind of immediate maintenance, in which materialized
views are updated
immediately after a base table is modified.
Source repository:
[https://github.com/sraoss/pg_ivm](https://github.com/sraoss/pg_ivm)
