Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wgjUY-006MWo-1u for pgsql-announce@arkaria.postgresql.org; Mon, 06 Jul 2026 13:36:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wgjUX-000W38-1C for pgsql-announce@arkaria.postgresql.org; Mon, 06 Jul 2026 13:36:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wgjUW-000W2j-1f for pgsql-announce@lists.postgresql.org; Mon, 06 Jul 2026 13:36:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wgjUU-00000001qsK-18lK for pgsql-announce@lists.postgresql.org; Mon, 06 Jul 2026 13:36:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=asE30+GiGpVyxq/JiEMRXx0ccgCI1YFpxhITuyYr6kI=; b=knPOt74/i1c0ZSpjbiTidz1qjp pGHD9Dr69f1nHRYNGDOI3HZaGdsO8kSDusncq/z/ry3vsrfYs7XOXyMIZrRJNBGb0kc+20WKHW0Ri M8jdRXeBOW3zzHcgRANc/m+yOX+Yc7Vxuh2J3SfSi4Ue7xg/2HBqsH4xi8ijbiKXw4fNGfQNUoz0E SuG9XhMAcgGeytt/f5cpKoyAssIy4TdB/K4eNlviqTSSAG2rgaCwmaQ357c65Ar2wKGSABf8fQ5xJ CbhcAj/wLe+MfM/b1aqil17xkgaP+4ua8IhF+CgBLSwv/Ms/e/K10msWYjF/+ajLnUqANAmO9RXWf 5OOCAikg==; Received: from wrigleys.postgresql.org ([217.196.149.60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wgjUT-00BaVj-1Y for pgsql-announce@lists.postgresql.org; Mon, 06 Jul 2026 13:36:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wgjUR-00EFEy-09 for pgsql-announce@lists.postgresql.org; Mon, 06 Jul 2026 13:36:03 +0000 Content-Type: multipart/alternative; boundary="===============8781069694558676811==" MIME-Version: 1.0 Subject: pg_ivm 1.15 released To: PostgreSQL Announce From: IVM Development Group via PostgreSQL Announce Reply-To: nagata@sraoss.co.jp Date: Mon, 06 Jul 2026 13:35:59 +0000 Message-ID: <178334495919.108999.13380389345437224054@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: bac682b1cef0c42305055ba0326cc573be5e7c57ea2b799c8192cbf7193258b1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============8781069694558676811== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 p= g_upgrade,=20 IMMVs no longer need to be dropped and recreated manually. The new pg_i= vm_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 R= I triggers, incremental maintenance could produce inconsistent results or lead to d= uplicate 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=20 (IVM) feature. Incremental View Maintenance (IVM) is a way to make materialized views=20 up-to-date in which only incremental changes are computed and applied on views rather=20 than recomputing. pg_ivm provides a kind of immediate maintenance, in which materialized=20 views are updated immediately after a base table is modified. Source repository:=20 [https://github.com/sraoss/pg_ivm](https://github.com/sraoss/pg_ivm) --===============8781069694558676811== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_ivm 1.15 released
 

pg_ivm 1.15 released

IVM Development Group is pleased to announc= e the release of pg_ivm 1.15.=

Changes since the v1.14 release include:

What's Changed

New features

  • Add IMMV metadata restore support for pg_du= mp and pg_upgrade (Yugo Nagata)

    After restoring a database from pg_dump or = upgrading PostgreSQL using pg_upgrade,=20 IMMVs no longer need to be dropped and recreated manually. The new pg_ivm_d= ump_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 tab= le is modified multiple times by triggers (Yugo Nagata)

    Previously, if a table was modified multipl= e times by user-defined or RI triggers, incremental maintenance could produce inconsistent results or lead to dupli= cate key violations.

  • Fix segfault during outer-join views mainte= nance (Yugo Nagata)

    This bug was introduced in v1.14.

About pg_ivm

pg_ivm is an extension module that provides= Incremental View Maintenance=20 (IVM) feature.

Incremental View Maintenance (IVM) is a way= to make materialized views=20 up-to-date in which only incremental changes are computed and applied on views rather=20 than recomputing. pg_ivm provides a kind of immediate maintenance, in which materialized=20 views are updated immediately after a base table is modified.

Source repository:=20 https://github.com/sraoss/pg_ivm
This email was sent to you from IVM Development Group. It was delivered on = their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to IVM Development Group.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============8781069694558676811==--