public inbox for [email protected]
help / color / mirror / Atom feedFrom: pg_hint_plan via PostgreSQL Announce <[email protected]>
To: PostgreSQL Announce <[email protected]>
Subject: pg_hint_plan v1.8.0 Released
Date: Sat, 23 Aug 2025 12:10:13 +0000
Message-ID: <[email protected]> (raw)
The pg_hint_plan development team is pleased to announce pg_hint_plan 1.8.0. This release of pg_hint_plan adds compatibility with PostgreSQL 18, and includes various improvements and bug fixes. For more details, see the [release notes](https://github.com/ossc-db/pg_hint_plan/releases). This new major version includes the following new features:
- Compatibility with PostgreSQL 18 (disabled nodes, self-join elimination, etc.)
- Addition of hint DisableIndex
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](https://github.com/ossc-db/pg_hint_plan/).
The documentation of the project is published at [this page](https://pg-hint-plan.readthedocs.io/), and is synced up automatically from the source repository.
A new set of minor releases is available down to PostgreSQL 13, each marked with the following versions:
* pg_hint_plan 1.7.1, compatible with PostgreSQL 17.
* pg_hint_plan 1.6.2, compatible with PostgreSQL 16.
* pg_hint_plan 1.5.3, compatible with PostgreSQL 15.
* pg_hint_plan 1.4.4, compatible with PostgreSQL 14.
* pg_hint_plan 1.3.11, compatible with PostgreSQL 13.
This is the last release planned for PostgreSQL 13.
pg_hint_plan v1.7.0 Released
Notable changes in this set of releases include the following bug fixes, where applicable:
- Fix assertion failure with incorrect number of workers
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: pg_hint_plan v1.8.0 Released
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox