Re: Multivariate MCV list vs. statistics target

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, "Jamison, Kirk" <k(dot)jamison(at)jp(dot)fujitsu(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Multivariate MCV list vs. statistics target
Date: 2019-09-10 22:28:12
Message-ID: 20190910222812.3o5kyf7ghie34gg2@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Sep 03, 2019 at 02:38:56PM -0400, Alvaro Herrera wrote:
>On 2019-Aug-01, Tomas Vondra wrote:
>> I'll move it to the next CF. Aside from the issues pointed by Kyotaro-san
>> in his review, I still haven't made my mind about whether to base the use
>> statistics targets set for the attributes. That's what we're doing now,
>> but I'm not sure it's a good idea after adding separate statistics target.
>> I wonder what Dean's opinion on this is, as he added the current logic.
>Latest patch no longer applies. Please update. And since you already
>seem to have handled all review comments since it was Ready for
>Committer, and you now know Dean's opinion on the remaining question,
>please get it pushed.

OK, I've pushed this the patch, after some minor polishing.


Tomas Vondra
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2019-09-10 22:30:25 Re: Planning counters in pg_stat_statements (using pgss_store)
Previous Message Tom Lane 2019-09-10 22:18:58 Re: [PATCH] Improve performance of NOTIFY over many databases (v2)