Fix selectivity estimation @> (anymultirange, anyrange) operator
Alexander Korotkov <akorotkov@postgresql.org>
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
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/utils/adt/multirangetypes_selfuncs.c | modified | +1 −0 |
| src/test/regress/expected/multirangetypes.out | modified | +5 −0 |
| src/test/regress/expected/rangetypes.out | modified | +5 −0 |
| src/test/regress/sql/multirangetypes.sql | modified | +6 −0 |
| src/test/regress/sql/rangetypes.sql | modified | +6 −0 |
Discussion
Cited messages not in the archive:
X+wmgjRItuvHNBeV@paquier.xyz