Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)

Maxim Boguk <maxim.boguk@gmail.com> writes:
> Reading the code - probably the lowest hanging fruit is to make
> 'The current multiplier of 1000 * cpu_operator_cost' configurable in the
> future versions.

I'm wondering whether we should try to make the planner not expend
the effort in the first place, but leave partition pruning to the
executor, at least in cases where it can determine that that will be
possible.

            regards, tom lane