pg_ivm 1.17 fixes restore problems in incremental views
The pg_ivm 1.17 PostgreSQL extension fixes a restore-state bug that could add duplicate triggers during a later view refresh. It also adds a metadata restore option for pg_upgrade and improves automatic unique-key detection for some queries, including those with EXISTS. pg_ivm keeps materialized views current by applying changes as base tables change.
PostgreSQL · Oct 26, 2026
Why it matters
Teams using incremental materialized views should review the restore fix before their next database upgrade or recovery drill.
More context
The release adds a replace option to restore_immv() and a --pg-upgrade option to pg_ivm_dump_metadata. The previous restore path could leave an incorrect ispopulated state, causing refresh_immv() to add duplicate maintenance triggers. The project is a PostgreSQL extension maintained separately from the database server.
Keep in mind
This release only applies to installations using pg_ivm. Review the extension's compatibility and migration guidance, then test restore and refresh behavior with a copy of your data.
Original read