public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andrei Lepikhov <[email protected]>
To: Andres Freund <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Alexander Lakhin <[email protected]>
Cc: Lukas Fittl <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: pg_plan_advice
Date: Mon, 6 Apr 2026 17:11:15 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <t27zi5nzsazkxlhvrrbbaaeqso7huqmtuoxtyk6vpdvl4xlx5c@eahhvqesniqn>
References: <CAP53Pkzn_wZ-R-cPdD9XSQ9+myPUUsPMMqVBPNG3XWXhgfm1-Q@mail.gmail.com>
<CA+Tgmobxbju8PrY_NULtPr7b7UShp4+Jqibm2Bou8TVS69gObQ@mail.gmail.com>
<[email protected]>
<CA+TgmoadkuOMJjvYe2h6aznHFeePprGEQ8CgUpRK=47sB6DMAg@mail.gmail.com>
<[email protected]>
<CA+TgmoY+g1u-fN=3igXG-8u0Ho3V4u-ooWXCj-FQ9DA=uGek9g@mail.gmail.com>
<[email protected]>
<[email protected]>
<CA+Tgmoben3_8rZbQ2X2+gOBOFpOgkc9hx3-z9e_Q_kHCfuW25g@mail.gmail.com>
<[email protected]>
<t27zi5nzsazkxlhvrrbbaaeqso7huqmtuoxtyk6vpdvl4xlx5c@eahhvqesniqn>
On 06/04/2026 15:56, Andres Freund wrote:
> You're making sweeping high-level demands, implying they're easy ("when I
> designed ... this kind of problem couldn’t have happened"), without any
> concrete technical suggestions for how to actually achieve that. In very
> strong language. Your high level demand, that somehow plan shape influencing
> code should just work regardless of what crazy thing extensions have done
> seems ... not entirely realistic, to put it very kindly.
Sorry about that.
I haven't had much practice with English. Sometimes, things I wouldn't
normally say in technical discussions in my native language come out
here. As well as part of the meaning definitely lost in translation.
The actual reason was to highlight that quite closely related features
exist in the Postgres world (not only pg_hint_plan). Even if we can’t
expose the code of enterprise forks, it worth to discuss alternative
design ideas.
--
regards, Andrei Lepikhov,
pgEdge
view thread (184+ messages) latest in thread
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], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: pg_plan_advice
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