Fix selectivity estimation @> (anymultirange, anyrange) operator
Attempt to get selectivity estimation for @> (anymultirange, anyrange) operator
caused an error in buildfarm, because this operator was missed in switch()
of calc_hist_selectivity(). Fix that and also make regression tests reliably
check that selectivity estimation for (multi)ranges doesn't fall. Previously,
whether we test selectivity estimation for (multi)ranges depended on
whether autovacuum managed to gather concurrently to the test.
Reported-by: Michael Paquier
Discussion: https://postgr.es/m/X%2BwmgjRItuvHNBeV%40paquier.xyz
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/62097a4cc8c725fa86d3170396a8f30609acd0d3
Modified Files
--------------
src/backend/utils/adt/multirangetypes_selfuncs.c | 1 +
src/test/regress/expected/multirangetypes.out | 5 +++++
src/test/regress/expected/rangetypes.out | 5 +++++
src/test/regress/sql/multirangetypes.sql | 6 ++++++
src/test/regress/sql/rangetypes.sql | 6 ++++++
5 files changed, 23 insertions(+)