Re: Postgresql 14/15/16/17 partition pruning on dependent table during join

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Stepan Yankevych <Stepan_Yankevych(at)epam(dot)com>, Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>
Cc: "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgresql 14/15/16/17 partition pruning on dependent table during join
Date: 2024-11-04 12:05:44
Message-ID: fbbb2de3-40b8-4bd1-a539-de101b7c6e98@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Andrei Lepikhov 2024-11-05 02:22:35 Re: Performance of Query 2 in TPC-H
Previous Message Laurenz Albe 2024-11-04 09:24:09 Re: proposal: schema variables