| From: | Alastair Turner <minion(at)decodable(dot)me> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_plan_advice |
| Date: | 2025-10-31 21:17:41 |
| Message-ID: | CAC0GmywDf5cs1_DoCyZwec=73Q5P7t88ikJ=LuKLXPO-Fd2LFQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 31 Oct 2025, 12:51 Robert Haas, <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Oct 31, 2025 at 5:59 AM Jakub Wartak
> <jakub(dot)wartak(at)enterprisedb(dot)com> wrote:
> > > First, any form of user control over the planner tends to be a
> lightning rod for criticism around here.
> >
> > I do not know where this is coming from, but everybody I've talked to
> > was saying this is needed to handle real enterprise databases and
> > applications. I just really love it, how one could precisely adjust
> > the plan with this even with the presence of heavy aliasing:
>
I really like the functionality of the current patch as well, even though I
am suspicious of user control over the planner. By giving concise, precise
control over a plan, this allows people who believe they can out-plan the
planner to test their alternative, and possibly fail.
Whatever other UIs and integrations you build as you develop this towards
you goal, please keep what's currently there user accessible. Not only for
testing code, but also for testing users' belief that they know better.
Alastair
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2025-10-31 21:30:19 | Re: Change initdb default to the builtin collation provider |
| Previous Message | Thomas Munro | 2025-10-31 21:13:38 | Re: meson's in-tree libpq header search order vs -Dextra_include_dirs |