Re: Performance of Query 2 in TPC-H

2024-11-04 Thread Andrei Lepikhov
On 11/4/24 15:42, Ba Jinsheng wrote: The estimated cost is reduced by 90%, and the execution time is reduced by 68%. The second query plan includes the operation Memoize, while the first query plan does not. I am wondering if we can optimize the logic anywhere to enable the second query plan.

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

2024-11-04 Thread Andrei Lepikhov
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

Performance of Query 2 in TPC-H

2024-11-04 Thread Ba Jinsheng
Please see this case: TPC-H query 2: select s_acctbal, s_name, n_name, p_partkey, p_mfgr, s_address, s_phone, s_comment from PART, SUPPLIER, PARTSUPP, NATION, REGION where p_partkey = ps_partkey and s_suppkey = ps_suppkey and p_size

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

2024-11-04 Thread Stepan Yankevych
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 Stepan Yanke