Re: Postgresql 14/15/16/17 partition pruning on dependent table during join - Mailing list pgsql-performance

From Andrei Lepikhov
Subject Re: Postgresql 14/15/16/17 partition pruning on dependent table during join
Date
Msg-id fbbb2de3-40b8-4bd1-a539-de101b7c6e98@gmail.com
Whole thread Raw
In response to Re: Postgresql 14/15/16/17 partition pruning on dependent table during join  (Stepan Yankevych <Stepan_Yankevych@epam.com>)
List pgsql-performance
On 4/11/2024 15:23, Stepan Yankevych wrote:
> Let's classify it as possible improvement / new feature for further 
> releases.
> Optimizer definitely should be able to add that extra (redundant) 
> condition *and e.exec_date_id >= 20241021*
> or even transform* e.exec_date_id >= co.create_date_id *
> to              *e.exec_date_id >= **20241021*
Not sure it would be easy (and make sense) to implement it as a core 
feature. But the idea of the extensibility of the clause deduction 
system looks spectacular to me.

-- 
regards, Andrei Lepikhov




pgsql-performance by date:

Previous
From: Ba Jinsheng
Date:
Subject: Performance of Query 2 in TPC-H
Next
From: Rafia Sabih
Date:
Subject: Re: Bloom filters and the planner / parallel execution