Re: Organize working memory under per-PlanState context

On 20/8/2025 01:34, Jeff Davis wrote:
> It doesn't do much yet, but it creates infrastructure that will be
> useful for subsequent patches to make the memory accounting and
> enforcement more consistent throughout the executor.Does this mean that you are considering flexible memory allocation
during execution based on a specific memory quota? If so, I believe this
should be taken into account during the optimisation stage. If the
planner calculates the cost of the nodes using only a single work_mem
value, it could lead to suboptimal execution. For example, this might
result in too many intermediate results being written to disk, which in
turn can reduce correlation between the estimated plan cost and the
actual execution time.

--
regards, Andrei Lepikhov