From: IVM Development Group via PostgreSQL Announce <announce-noreply@postgresql.org>
To: PostgreSQL Announce <pgsql-announce@lists.postgresql.org>
Subject: pg_ivm 1.16 released
Date: Mon, 05 Oct 2026 01:15:14 +0000
Message-ID: <179116291489.1253.2942601804087045098@wrigleys.postgresql.org> (raw)
IVM Development Group is pleased to announce the release of [pg_ivm 1.16]( https://github.com/sraoss/pg_ivm/releases/tag/v1.16 ).
Changes since the v1.15 release include:
## What's Changed
### New features
* Add support for PostgreSQL 19 ( Devrim Gündüz )
### Bug fixes
* Fix a segfault when an IMMV is maintained and dropped in the same transaction (Yugo Nagata)
* Fix IVM maintenance for tables without default equality operators (Yugo Nagata)
When a base table contained a type without a default equality operator, maintenance of the views
failed when the table was updated, even if the column was not referenced by the view definition.
* Fix OID handling when OID exceeds INT_MAX (Artur Aleksander Kanošin)
View maintenance failed when the global OID counter exceeds INT_MAX.
* Prevent spurious transaction failures during incremental maintenance (Dzmitry Levankou)
During incremental maintenance, locks are acquired on the materialized view to
prevent anomalies caused by concurrent maintenance. Previously, due to the timing
of lock release during commit, a transaction could fail unnecessarily with a lock error
even though no concurrent incremental maintenance was actually in progress. This
issue could also make isolation tests fail intermittently under load.
### 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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-announce@postgresql.org
Cc: announce-noreply@postgresql.org, pgsql-announce@lists.postgresql.org
Subject: Re: pg_ivm 1.16 released
In-Reply-To: <179116291489.1253.2942601804087045098@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox