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.98.2) (envelope-from ) id 1xDXPS-00000000ZJW-3rPh for pgsql-announce@arkaria.postgresql.org; Mon, 05 Oct 2026 01:22:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xDXPR-00000006jGF-1b2M for pgsql-announce@arkaria.postgresql.org; Mon, 05 Oct 2026 01:22:29 +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.98.2) (envelope-from ) id 1xDXJL-00000006NhJ-00Iz for pgsql-announce@lists.postgresql.org; Mon, 05 Oct 2026 01:16:11 +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 1xDXJG-00000000O3z-18pc for pgsql-announce@lists.postgresql.org; Mon, 05 Oct 2026 01:16:10 +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=cCGoPaZIRCQFZlw8vwVtVQSKZS7X6pXEWDd7qZmo/hE=; b=Gnsn3jdW62B9ggQb+vUPMcJNt5 cqoN6xh0YeWbme7XU7FfaN0rdwhEIAh802iGF2RJtYrd/x7IfPltGMZl6VhTahl6rsqvO9C352e0g YTA/Ubad0HFS37YykezERCZaoT5DNzBuw3YBpTeLim82y7cIAA85XCHMp7S5ho+mEQbiOFrv1YIc2 0g9+Vii5EhQ+9SfzNHNsI4GCqCmhWPpTv6roseBmejG1YrayAfhUNU2eXBeZLBuNNssz757ZN5koA Fc6hVJzXKL4kAzSEsfQbeTLCUYlqj+G2qfObuHXgZxNq7mxtYiOyrMucgOtAw+yOfdKgQrzK7cN4o ojHjJ/JQ==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xDXJF-00000001IyF-2EOF for pgsql-announce@lists.postgresql.org; Mon, 05 Oct 2026 01:16:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xDXJD-00000003VJF-3hz1 for pgsql-announce@lists.postgresql.org; Mon, 05 Oct 2026 01:16:03 +0000 Content-Type: multipart/alternative; boundary="===============2483308378577897454==" MIME-Version: 1.0 Subject: pg_ivm 1.16 released To: PostgreSQL Announce From: IVM Development Group via PostgreSQL Announce Reply-To: nagata@sraoss.co.jp Date: Mon, 05 Oct 2026 01:15:14 +0000 Message-ID: <179116291489.1253.2942601804087045098@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 877967be38366952fd579c0380454883a538809c846aa5a8c431733d9e4a6afd List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============2483308378577897454== 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.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=C3=BCnd=C3=BCz ) ### Bug fixes * Fix a segfault when an IMMV is maintained and dropped in the same transac= tion (Yugo Nagata) * Fix IVM maintenance for tables without default equality operators (Yugo N= agata) 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 reference= d by the view definition. * Fix OID handling when OID exceeds INT_MAX (Artur Aleksander Kano=C5=A1in) View maintenance failed when the global OID counter exceeds INT_MAX. * Prevent spurious transaction failures during incremental maintenance (Dzm= itry 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 w= ith a lock error even though no concurrent incremental maintenance was actually in progr= ess. 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=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) --===============2483308378577897454== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_ivm 1.16 released
 

pg_ivm 1.16 released

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

Changes since the v1.15 release include:

What's Changed

New features

  • Add support for= PostgreSQL 19 ( Devrim G=C3=BCnd=C3=BCz )

Bug fixes

  • Fix a segfault when an IMMV is maintained a= nd dropped in the same transaction (Yugo Nagata)

  • Fix IVM maintenance for tables without defa= ult 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=C5=A1in)

    View maintenance failed when the global OID= counter exceeds INT_MAX.

  • Prevent spurious transaction failures durin= g incremental maintenance (Dzmitry Levankou)

    During incremental maintenance, locks are a= cquired 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=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/.
 
--===============2483308378577897454==--