From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: significant semi join overestimates (with CTEs) |
Date: | 2016-02-24 06:05:35 |
Message-ID: | CA+TgmobgZ6_7rWUyPdjmkZKjvgjzhe0QdLONo7f=ytMcRUARnA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 22, 2016 at 4:32 AM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> Firstly, we could clamp the join cardinality estimate to the size of
> cartesian product, eliminating at least the most obvious over-estimates.
>
> Secondly, I think it'd be nice to somehow eliminate the sudden jumps in the
> estimates - I'm not quite sure why need the three different formulas in
> eqjoinsel_semi, so maybe we can get rid of some of them?
I don't have any particularly intelligent commentary on the second
point right at the moment, but I emphatically agree with you on the
first one. I've seen that problem a number of times and it seems
completely ludicrous to me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-02-24 06:23:30 | Re: Allow to specify (auto-)vacuum cost limits relative to the database/cluster size? |
Previous Message | Robert Haas | 2016-02-24 05:56:50 | Re: GIN data corruption bug(s) in 9.6devel |