IVM Development Group is pleased to announce the release of [pg_ivm 1.3](
https://github.com/sraoss/pg_ivm/releases/tag/v1.3 ).
Changes since the v1.2 release include:
### New feature
* Add get_immv_def function (Takuma Hoshiai)
This function reconstructs the underlying SELECT command for an IMMV.
### Bug fixes
* Fix a maintenance failure of MIN/MAX aggregate views whose columns had alias
names (Yugo Nagata)
Views that have a min/max aggregate with an alias name (e.g. `min(j) as
min_j`) were not correctly handled and an error could be raised when a tuple
was deleted from a base table.
* Fix possible incorrect maintenance due to XID wraparound or using
sub-transactions (Yugo Nagata)
* Fix a bug that any table cannot be dropped by non-superuser (Yugo Nagata)
### 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)
