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.94.2) (envelope-from ) id 1rh17V-0099go-AC for pgsql-announce@arkaria.postgresql.org; Mon, 04 Mar 2024 05:44:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rh17R-004idF-ST for pgsql-announce@arkaria.postgresql.org; Mon, 04 Mar 2024 05:44:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rh17Q-004id6-OB for pgsql-announce@lists.postgresql.org; Mon, 04 Mar 2024 05:44:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rh17N-002fM2-H8 for pgsql-announce@lists.postgresql.org; Mon, 04 Mar 2024 05:44:08 +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=t9ZKjoE5w8Ayy8SLqqK9EEVGhYo64k3/vmpEjNYsg/o=; b=vYTYf26OZx6HhvX9Vs9VpIp8Qc D+mNl4K5CcT9B0wVz6fngCu3U56yYnQRRguVrC9EKseAMarZwgxL1Jfj8OH1FsqTc0xKEaf0bNiUJ Swb5JG6eyndmTlxJtZyoSyj5ITdttO04OGdGfQu5Ao9OHJQR2pH7wZVSe69bVE3suFxIl0MsH3DPw 2kR/LYzwtCcaocU+FV0Av8zcaqOsOCim/RrpFxE2vSghS2VtpSpFqEyv9J+rvDIRzEx0swhotkMuz BwIFFLjewj7+pl4m8lMWTf4CTxq/zwTllm3CakBNk6ssYOEYjNJgulSyBafAovLqELAfNj9aIEjGx 2hHvywAw==; Received: from wrigleys.postgresql.org ([2a02:c0:301:0:ffff::34]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rh17L-006Q1b-2F for pgsql-announce@lists.postgresql.org; Mon, 04 Mar 2024 05:44:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rh17J-00H5Sw-BD for pgsql-announce@lists.postgresql.org; Mon, 04 Mar 2024 05:44:02 +0000 Content-Type: multipart/mixed; boundary="===============5880730254560403835==" MIME-Version: 1.0 Subject: pg_ivm 1.8 released To: PostgreSQL Announce From: IVM Development Group via PostgreSQL Announce Reply-To: nagata@sraoss.co.jp Date: Mon, 04 Mar 2024 05:43:53 +0000 Message-ID: <170953103346.639.12007177220678418957@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 880fa813cbf0722c25af2e33795b4f5d4e46afedd08e2102b9e809378343a855 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============5880730254560403835== Content-Type: multipart/alternative; boundary="===============4329812869545211710==" MIME-Version: 1.0 --===============4329812869545211710== 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.8]( h= ttps://github.com/sraoss/pg_ivm/releases/tag/v1.8 ). Changes since the v1.7 release include: ### Bug fixes * Consider tuple duplicity in maintenance of EXISTS views (Yugo Nagata) Previously, the duplicity of row was not considered and only one tuple = was inserted even when duplicated tuples are generated as a result of inserting a tu= ple into a table in an EXISTS subquery. * Fix checking for expressions containing an EXISTS subquery (Takuma Hoshia= i, Yugo Nagata) EXISTS subquery is currently allowed only directly under WHERE clause o= r in AND expression that is directly under WHERE. However, the check was insuffi= cient previously so that views using expressions other than AND containing an EXISTS sub= query could be created without an error and it caused incorrect maintenance results. * Check if PgIvmImmvRelationId is invalid before open it (Colin Zhao) Fix an error that occurs at dropping tables that occurs when pg_ivm is = installed by shared_preload_libraries without executing CREATE EXTENSION command. * Fix an error raised when dropping pg_ivm extension (Yugo Nagata) Previously, DROP EXTENSION pg_ivm failed due to the failure of opening = the index on the pg_ivm_immv catalog table, because the index had been already dr= opped at that time. ### About pg_ivm pg_ivm is an extension module that provides Incremental View Maintenance (I= VM) feature. Incremental View Maintenance (IVM) is a way to make materialized views up-t= o-date in which only incremental changes are computed and applied on views rather tha= n recomputing.=20 pg_ivm provides a kind of immediate maintenance, in which materialized view= s are updated immediately after a base table is modified. =20 Source repository: [https://github.com/sraoss/pg_ivm](https://github.com/sr= aoss/pg_ivm) --===============4329812869545211710== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_ivm 1.8 released
 

pg_ivm 1.8 released

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

Changes since the v1.7 release include:

Bug fixes

  • Consider tuple duplicity in maintenance of = EXISTS views (Yugo Nagata)

    Previously, the duplicity of row was not co= nsidered and only one tuple was inserted even when duplicated tuples are generated as a result of inserting a tuple = into a table in an EXISTS subquery.

  • Fix checking for expressions containing an = EXISTS subquery (Takuma Hoshiai, Yugo Nagata)

    EXISTS subquery is currently allowed only d= irectly under WHERE clause or in AND expression that is directly under WHERE. However, the check was insufficien= t previously so that views using expressions other than AND containing an EXISTS subquer= y could be created without an error and it caused incorrect maintenance results.

  • Check if PgIvmImmvRelationId is invalid bef= ore open it (Colin Zhao)

    Fix an error that occurs at dropping tables= that occurs when pg_ivm is installed by shared_preload_libraries without executing CREATE EXTENSION command.

  • Fix an error raised when dropping pg_ivm ex= tension (Yugo Nagata)

    Previously, DROP EXTENSION pg_ivm failed du= e to the failure of opening the index on the pg_ivm_immv catalog table, because the index had been already dropped at that time.

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 tha= n recomputing.=20 pg_ivm provides a kind of immediate maintenance, in which materialized view= s are updated immediately after a base table is modified.

Source repository: h= ttps://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/.
 
--===============4329812869545211710==-- --===============5880730254560403835==--