Request a Demo
Home   >   mailing lists

Re: pg_plan_advice - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_plan_advice
Date
Msg-id CA+TgmobRs1a3ctr=_3DozWR4Ftxb0jqrRfZR-hNiGghCcq2AXg@mail.gmail.com
Whole thread Raw
In response to Re: pg_plan_advice  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
On Thu, Feb 12, 2026 at 8:08 AM Robert Haas <robertmhaas@gmail.com> wrote:
> 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

sorry, this should have said "doesn't cause"

> 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.

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

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Add 64-bit XIDs into PostgreSQL 15
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Add file_extend_method=posix_fallocate,write_zeros.