Multivariate MCV list vs. statistics target

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Multivariate MCV list vs. statistics target
Date: 2019-06-18 21:33:57
Message-ID: 20190618213357.vli3i23vpkset2xd@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


One slightly inconvenient thing I realized while playing with the
address data set is that it's somewhat difficult to set the desired size
of the multi-column MCV list.

At the moment, we simply use the maximum statistic target for attributes
the MCV list is built on. But that does not allow keeping default size
for per-column stats, and only increase size of multi-column MCV lists.

So I'm thinking we should allow tweaking the statistics for extended
stats, and serialize it in the pg_statistic_ext catalog. Any opinions
why that would be a bad idea?

I suppose it should be part of the CREATE STATISTICS command, but I'm
not sure what'd be the best syntax. We might also have something more
similar to ALTER COLUMNT, but perhaps


looks a bit too weird.


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


Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2019-06-18 21:43:13 O(N^2) when building multi-column MCV lists
Previous Message David Fetter 2019-06-18 21:15:25 Re: New EXPLAIN option: ALL