Prefer actual constants to pseudo-constants in equivalence class machinery.

generate_base_implied_equalities_const() should prefer plain Consts over
other em_is_const eclass members when choosing the "pivot" value that
all the other members will be equated to.  This makes it more likely that
the generated equalities will be useful in constraint-exclusion proofs.
Per report from Rushabh Lathia.

diff --git a/src/backend/optimizer/path/equivclass.c b/src/backend/optimizer/path/equivclass.c
index 9bc830bc35c170560cca17ee81165b55a1a92185..58553df3140f03278b8f6e8effdfe7e01615367a 100644 (file)
--- a/src/backend/optimizer/path/equivclass.c
+++ b/src/backend/optimizer/path/equivclass.c
@@ -769,7 +769,12 @@ generate_base_implied_equalities_const(PlannerInfo *root,
                }
        }
 
-       /* Find the constant member to use */
+       /*
+        * Find the constant member to use.  We prefer an actual constant to
+        * pseudo-constants (such as Params), because the constraint exclusion
+        * machinery might be able to exclude relations on the basis of generated
+        * "var = const" equalities, but "var = param" won't work for that.
+        */
        foreach(lc, ec->ec_members)
        {
                EquivalenceMember *cur_em = (EquivalenceMember *) lfirst(lc);
@@ -777,7 +782,8 @@ generate_base_implied_equalities_const(PlannerInfo *root,
                if (cur_em->em_is_const)
                {
                        const_em = cur_em;
-                       break;
+                       if (IsA(cur_em->em_expr, Const))
+                               break;
                }
        }
        Assert(const_em != NULL);