Re: pg_plan_advice - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_plan_advice
Date
Msg-id CA+TgmoYg8Ft9CZWD2GVGn1Qt6EQTuHUuG_MkDaQ6XGD1doTK0w@mail.gmail.com
Whole thread
In response to Re: pg_plan_advice  (Ajay Pal <ajay.pal.k@gmail.com>)
Responses Re: pg_plan_advice
List pgsql-hackers
On Thu, Feb 12, 2026 at 6:41 AM Ajay Pal <ajay.pal.k@gmail.com> wrote:
> pg_plan_advice failed to match JOIN_ORDER advice because the genetic
> algorithm never attempts the specific join path requested.

Seems expected. It is bad if using GEQO results in a crash or if the
advice cause the expected outcome when the path is considered, but if
the randomness of GEQO causes it not to consider the path the user
wants, then the user either needs to stop using GEQO, or use
less-strict plan advice, or just understand that this kind of outcome
is a possibility.

Thanks,

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Yura Sokolov
Date:
Subject: Re: Add 64-bit XIDs into PostgreSQL 15
Next
From: Jakub Wartak
Date:
Subject: Re: Changing shared_buffers without restart