MIME-Version: 1.0
References: 
 <CA+TgmoZ-Jh1T6QyWoCODMVQdhTUPYkaZjWztzP1En4=ZHoKPzw@mail.gmail.com>
 <CAKZiRmxtJAFG7e1+Vs9B8ngON=AOzJbuws+1ZeH4LsbJh5AzoQ@mail.gmail.com>
 <CA+TgmoZf1F360z6jNVZyv7UF=URSNvCWbsCX7A_nsH=iaEqm0A@mail.gmail.com>
 <CAC0GmywDf5cs1_DoCyZwec=73Q5P7t88ikJ=LuKLXPO-Fd2LFQ@mail.gmail.com>
 <CAMT0RQRUgzc2kKLqs1goXZkMgrJ5p_TpP9BME6dn0i5RxKAH+A@mail.gmail.com>
In-Reply-To: 
 <CAMT0RQRUgzc2kKLqs1goXZkMgrJ5p_TpP9BME6dn0i5RxKAH+A@mail.gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
Date: Mon, 3 Nov 2025 11:41:35 -0500
Message-ID: 
 <CA+TgmoZzcyFSZjuSGA3CEpddHNZtxT36e_+MrpNz5eeEjuN+Jg@mail.gmail.com>
Subject: Re: pg_plan_advice
To: Hannu Krosing <hannuk@google.com>
Cc: Jakub Wartak <jakub.wartak@enterprisedb.com>,
 Alastair Turner <minion@decodable.me>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BTgmoZzcyFSZjuSGA3CEpddHNZtxT36e_%2BMrpNz5eeEjuN%2BJg%40mail.gmail.com>
Precedence: bulk

On Sat, Nov 1, 2025 at 12:10=E2=80=AFPM Hannu Krosing <hannuk@google.com> w=
rote:
> This reinforces my belief thet we either should have some kind of
> two-level optimization, where most queries are handled quickly but
> with something to trigger a more elaborate optimisation and
> investigation workflow.
>
> Or alternatively we could just have an extra layer before the query is
> sent to the database which deals with unwinding the product of
> excessively stupid query generators (usually, but not always, some BI
> tools :) )

I'd like to keep the focus of this thread on the patches that I'm
proposing, rather than other ideas for improving the planner. I
actually agree with you that at least the first of these things might
be a very good idea, but that would be an entirely separate project
from these patches, and I feel a lot more qualified to do this project
than that one.

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