| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Mark Dilger <hornschnorter(at)gmail(dot)com>, Adrien Nayrat <adrien(dot)nayrat(at)dalibo(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] PATCH: multivariate histograms and MCV lists |
| Date: | 2018-04-07 14:12:01 |
| Message-ID: | 20180407141201.GA10394@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 1, 2018 at 06:07:55PM +0200, Tomas Vondra wrote:
> Hi,
>
> The attached patch version modifies how the non-MCV selectivity is
> computed, along the lines explained in the previous message.
>
> The comments in statext_clauselist_selectivity() explain it in far more
> detail, but we this:
Uh, where are we on this patch? It isn't going to make it into PG 11?
Feature development for this has been going on for years. I thought
when Dean Rasheed got involved that it would be applied for this
release.
I realize this is a complex feature, but I think it will solve 80-90% of
optimizer complaints, and I don't see any other way to fix them than
this. This seems like the right way to fix optimizer problems, instead
of optimizer hints.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2018-04-07 14:17:06 | Re: [HACKERS] GSoC 2017: weekly progress reports (week 4) and patch for hash index |
| Previous Message | Alexander Korotkov | 2018-04-07 14:10:44 | Re: [HACKERS] [PATCH] Incremental sort |