> On 6/5/25 17:42, Mark Frost wrote: > > Is there any good explanation for this behaviour? Preferably we’d like > > some way for proper `most_common_elems` statistics to be collected in > > our production database, in the hope that influences a good query plan > > to always be selected.
> most_common_elems has a limited size, and if all the elements have the > same freq, there's nothing we can do. > You could do: alter table test alter column tags set statistics X; > However, X is capped at 10000… Actually *any* most_common_elems stats would be fine, because the reasoning is: * If the searched element is in most_common_elems we know it’s frequency * If it’s not, it’s less frequent than the least most_common_elems So in our case when every row is unique, we’d only actually need stats to record a single most_common_elems (if only it would record one) Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN
