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

2025-05-13 Thread Maxim Boguk
On Mon, May 12, 2025 at 9:07 PM Tom Lane wrote: > Maxim Boguk 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. Is the 100x backend memory usage per cached plan differenc

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

2025-05-13 Thread David Rowley
On Tue, 13 May 2025 at 03:19, Maxim Boguk wrote: > On Mon, May 12, 2025 at 6:01 PM David Rowley wrote: >> This is just an artifact of the fact that runtime pruning is not factored >> into the costs. Note the cost of the generic plan. The plan_cache_mode GUC >> is about the only way to overrule