Re: pg_plan_advice - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: pg_plan_advice
Date
Msg-id 7d2526ac-d688-4b1a-bd49-70581d01b5fc@gmail.com
Whole thread Raw
In response to Re: pg_plan_advice  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PG 19 release notes and authors
Next
From: "David G. Johnston"
Date:
Subject: Re: PG 19 release notes and authors