Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17) - Mailing list pgsql-performance

From Andrei Lepikhov
Subject Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)
Date
Msg-id a949410c-acd6-4a93-b49b-a050dd949671@gmail.com
Whole thread Raw
In response to Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On 5/12/25 20:07, Tom Lane wrote:
> 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.
Significant planning time is a sorting out lots of scan paths, applying 
partition statistics etc. planner-stage partitioning reduces these 
efforts drastically.

-- 
regards, Andrei Lepikhov



pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)
Next
From: David Rowley
Date:
Subject: Re: inefficient/wrong plan cache mode selection for queries with partitioned tables (postgresql 17)