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 1sjw5F-005m88-6j for pgsql-announce@arkaria.postgresql.org; Fri, 30 Aug 2024 07:30:13 +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 1sjw5D-00GPux-D9 for pgsql-announce@arkaria.postgresql.org; Fri, 30 Aug 2024 07:30:11 +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 1sjw5C-00GPty-Ap for pgsql-announce@lists.postgresql.org; Fri, 30 Aug 2024 07:30: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.94.2) (envelope-from ) id 1sjw57-0028lj-RK for pgsql-announce@lists.postgresql.org; Fri, 30 Aug 2024 07:30:09 +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=KNL6O/ccxSjMdJUz6ZQWyoNB57BFLKRYyJ9U6YChl7k=; b=P8Rv/0oO50beX+AabAgkgT5ZfA 686z9kum+uDIkEwXFs8Lqfzh6uSWaHNuF2S+J9LXFwklOUiPE8FFIKLLOA2+AcsejF+JHyEoKeA3I pnufPSWWB7QvToulbIEW/vnv1RWh4YmyXwAV18T/5P3OW+KAujMgAiZLSU0jCMF4OeiNm8J83WMbr CIyvVHjWuzn+KDG47sjAfzMoB2GPGnkkYnZbAPgh6ytcxNF7GJeAW81Wce0uKHwjx2dnKoPvrog4G rFb4w4/t/h7+dRWFnQP7WVZKPgq4XmivvytT0HAS3KHaSRxn3B7y/eUGEOaDKB0xnDbywpS34pzKv N6676S+A==; 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 1sjw56-0075XT-KK for pgsql-announce@lists.postgresql.org; Fri, 30 Aug 2024 07:30: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 1sjw55-00A3MN-48 for pgsql-announce@lists.postgresql.org; Fri, 30 Aug 2024 07:30:03 +0000 Content-Type: multipart/mixed; boundary="===============6019069667691844702==" MIME-Version: 1.0 Subject: pg_hint_plan v1.7.0 Released To: PostgreSQL Announce From: pg_hint_plan via PostgreSQL Announce Reply-To: michael@paquier.xyz Date: Fri, 30 Aug 2024 07:29:38 +0000 Message-ID: <172500297865.862888.2481106132797022638@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: a035a50d355c70fce135daa43c88aa82d6612f462ec82370f5fbd361fda715b6 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============6019069667691844702== Content-Type: multipart/alternative; boundary="===============8101605386757090819==" MIME-Version: 1.0 --===============8101605386757090819== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable The pg_hint_plan development team is pleased to announce pg_hint_plan 1.7.0= . This release of pg_hint_plan adds compatibility with PostgreSQL 17, and = includes various improvements and bug fixes. For more details, see the [re= lease notes](https://github.com/ossc-db/pg_hint_plan/releases). This new ma= jor version includes the following new features: - Addition of a lexer to parse the query indexes. - Integration of query IDs with the hint table, instead of normalized strin= gs. - Removal of pg_hint_plan.hints_anywhere. pg_hint_plan is a PostgreSQL extension that offers the possibility to tweak= PostgreSQL execution plans using so-called "hints" in SQL comments. For mo= re information, see [the project page](https://github.com/ossc-db/pg_hint_p= lan/). The documentation of the project is published at [this page](https://pg-hin= t-plan.readthedocs.io/), and is synced up automatically from the source rep= ository. A new set of minor releases is available down to PostgreSQL 12, each marked= with the following versions: * pg_hint_plan 1.6.1, compatible with PostgreSQL 16. * pg_hint_plan 1.5.2, compatible with PostgreSQL 15. * pg_hint_plan 1.4.3, compatible with PostgreSQL 14. * pg_hint_plan 1.3.10, compatible with PostgreSQL 12 and 13. This is the last release planned for PostgreSQL 12. Notable changes in this set of releases include the following bug fixes, wh= ere applicable: - Revert improvement related to the handling of unavailable indexes in Scan= hints. This has proved to cause unwelcome plan instabilities, so this has = been removed for all stable branches. - Handle better the hint table if the extension is not created. - Various improvements and fixes to documentation and regression test suite. - Addition of META.json to distribute the module in PGXN. - Fix crash when retrieving query hint, impacting only PostgreSQL 12 and 13. --===============8101605386757090819== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_hint_plan v1.7.0 Released
 

pg_hint_plan v1.7.0 Released

The pg_hint_plan development team is please= d to announce pg_hint_plan 1.7.0. This release of pg_hint_plan adds compat= ibility with PostgreSQL 17, and includes various improvements and bug fixes= . For more details, see the release= notes. This new major version includes the following new features:

  • Addition of a l= exer to parse the query indexes.
  • Integration of = query IDs with the hint table, instead of normalized strings.
  • Removal of pg_h= int_plan.hints_anywhere.

pg_hint_plan is a PostgreSQL extension that= offers the possibility to tweak PostgreSQL execution plans using so-called= "hints" in SQL comments. For more information, see the project page.

The documentation of the project is publish= ed at this page, and is synced up automatica= lly from the source repository.

A new set of minor releases is available do= wn to PostgreSQL 12, each marked with the following versions:

  • pg_hint_plan 1.= 6.1, compatible with PostgreSQL 16.
  • pg_hint_plan 1.= 5.2, compatible with PostgreSQL 15.
  • pg_hint_plan 1.= 4.3, compatible with PostgreSQL 14.
  • pg_hint_plan 1.= 3.10, compatible with PostgreSQL 12 and 13.

This is the last release planned for Postgr= eSQL 12.

Notable changes in this set of releases inc= lude the following bug fixes, where applicable:

  • Revert improvem= ent related to the handling of unavailable indexes in Scan hints. This has = proved to cause unwelcome plan instabilities, so this has been removed for = all stable branches.
  • Handle better t= he hint table if the extension is not created.
  • Various improve= ments and fixes to documentation and regression test suite.
  • Addition of MET= A.json to distribute the module in PGXN.
  • Fix crash when = retrieving query hint, impacting only PostgreSQL 12 and 13.
This email was sent to you from pg_hint_plan. It was delivered on their beh= alf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to pg_hint_plan.

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/.
 
--===============8101605386757090819==-- --===============6019069667691844702==--