Re: Use merge-based matching for MCVs in eqjoinsel

From: David Geier <geidav(dot)pg(at)gmail(dot)com>
To: Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Use merge-based matching for MCVs in eqjoinsel
Date: 2025-09-08 07:11:24
Message-ID: b1f88b2b-99ed-40f2-b923-9f8a4ff4d1ac@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

On 03.09.2025 18:53, Ilia Evdokimov wrote:
> Following up on my previous messages about optimizing eqjoinsel() and
> eqjoinsel_semi() for Var1 = Var2 clauses, I’d like to share detailed
> profiling results showing the effect of the patch on JOB for different
> values of default_statistics_target.
>
> The first table shows the total planner time (summed over all 113
> queries) before and after applying the patch, along with the speedup
> achieved:
>
> default_statistics_target | Planner Speedup (×) | Planner Before (ms) |
> Planner After (ms)
> --------------------------+---------------------+---------------------
> +--------------------
> 100 | *1.00x* | 1828.433 | 1820.556
> 1000 | *1.12x* | 2194.282 | 1963.110
> 2500 | *2.15x* | 4606.705 | 2140.126
> 5000 | *6.37x* | 16661.581 |
2616.109
> 7500 | *11.76x* | 35988.569 |
> 3061.161
> 10000 | *19.01x* | 66616.620 |
> 3504.144
>

It looks to me like these results are with optimizations disabled?

Can you share the SQL script you used for testing?

--
David Geier

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-09-08 07:13:04 Re: Conflict detection for update_deleted in logical replication
Previous Message Laurenz Albe 2025-09-08 07:03:24 Re: Set log_lock_waits=on by default