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 1sZ9rD-00GmtI-K2 for pgsql-announce@arkaria.postgresql.org; Wed, 31 Jul 2024 13:59:11 +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 1sZ9rB-007JvA-J6 for pgsql-announce@arkaria.postgresql.org; Wed, 31 Jul 2024 13:59: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.94.2) (envelope-from ) id 1sZ9rA-007Jt5-Ji for pgsql-announce@lists.postgresql.org; Wed, 31 Jul 2024 13:59: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.94.2) (envelope-from ) id 1sZ9r7-002NsU-Sd for pgsql-announce@lists.postgresql.org; Wed, 31 Jul 2024 13:59: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=zt6XcPB63gjk65NpByvvd9eRv/JvTeKMdygFtOAUeNY=; b=KS/KJHtRCYnhXcSMJ+ZiksK3WW tKJUfQuZE34vaexet9oCTR0SNdTMaRsDzSR4DIrsfidBtKWlr2Tmh1SYA69l3CuK3vq+4rhyELQ9s O5FDB/VVJMPHXthzOl4Eo2A6jc1KXXHdsQXqY4wxS312H6PZzVdy+X20AQjDGT7nHywUARkvLwJ5d jRWIUC24/ImGq4E5ZKKxGbZ5sVBCyLBCkZxQtq1KmY3hWtTF96m5KwRfbfbYGDEGQKYw1nteEhlHS Q4LRGtU55CvGEPrSMcN8xP7euHIxf9n/2DmhwfkhDReHn4V7h3ikiweFtpFjMFuW8Zxj0bQmP5ddF x0LWBf6A==; 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.94.2) (envelope-from ) id 1sZ9r6-007RsF-S9 for pgsql-announce@lists.postgresql.org; Wed, 31 Jul 2024 13:59:05 +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 1sZ9r4-00AwCu-DQ for pgsql-announce@lists.postgresql.org; Wed, 31 Jul 2024 13:59:03 +0000 Content-Type: multipart/mixed; boundary="===============5405409866294833111==" MIME-Version: 1.0 Subject: pg_ivm 1.9 released To: PostgreSQL Announce From: IVM Development Group via PostgreSQL Announce Reply-To: nagata@sraoss.co.jp Date: Wed, 31 Jul 2024 13:58:36 +0000 Message-ID: <172243431643.915373.3788895852709899170@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: bb4bd5dc68ed943c3db068a9f528923e9230859eecaa9bdb91974fe27bb47abe List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============5405409866294833111== Content-Type: multipart/alternative; boundary="===============2057840201293055542==" MIME-Version: 1.0 --===============2057840201293055542== 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.9]( h= ttps://github.com/sraoss/pg_ivm/releases/tag/v1.9 ). Changes since the v1.8 release include: ### Bug fixes * Add support for PostgreSQL 17 (Yugo Nagata, Takuma Hoshiai, reshke) This contains the following changes: - Change functions to use a safe search_path during maintenance operations= when used with PostgreSQL 17 This prevents maintenance operations (automatic maintenance of IMMVs an= d refresh_immv) from performing unsafe access. Functions used by IMMVs that need to reference non-defau= lt schemas must specify a search path during function creation. - refresh_immv can be executed by users with the MAINTAIN privilege when u= sed with PostgreSQL 17 ### 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) --===============2057840201293055542== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_ivm 1.9 released
 

pg_ivm 1.9 released

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

Changes since the v1.8 release include:

Bug fixes

  • Add support for PostgreSQL 17 (Yugo Nagata,= Takuma Hoshiai, reshke)

    This contains the following changes:

  • Change functions to use a safe search_path = during maintenance operations when used with PostgreSQL 17

    This prevents maintenance operations (autom= atic maintenance of IMMVs and refresh_immv) from performing unsafe access. Functions used by IMMVs that need to reference non-default s= chemas must specify a search path during function creation.

  • refresh_immv can be executed by users with = the MAINTAIN privilege when used with PostgreSQL 17

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/.
 
--===============2057840201293055542==-- --===============5405409866294833111==--