pgsql: Rework examine_opclause_expression to use varonleft - Mailing list pgsql-committers

From Tomas Vondra
Subject pgsql: Rework examine_opclause_expression to use varonleft
Date
Msg-id E1hoqUa-0001ax-SY@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Rework examine_opclause_expression to use varonleft

The examine_opclause_expression function needs to return information on
which side of the operator we found the Var, but the variable was called
"isgt" which is rather misleading (it assumes the operator is either
less-than or greater-than, but it may be equality or something else).
Other places in the planner use a variable called "varonleft" for this
purpose, so just adopt the same convention here.

The code also assumed we don't care about this flag for equality, as
(Var = Const) and (Const = Var) should be the same thing. But that does
not work for cross-type operators, in which case we need to pass the
parameters to the procedure in the right order. So just use the same
code for all types of expressions.

This means we don't need to care about the selectivity estimation
function anymore, at least not in this code. We should only get the
supported cases here (thanks to statext_is_compatible_clause).

Reviewed-by: Tom Lane
Discussion: https://postgr.es/m/8736jdhbhc.fsf%40ansel.ydns.eu
Backpatch-to: 12

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/e38a55ba46bbd2510baccdbaa01298cbca972b88

Modified Files
--------------
src/backend/statistics/extended_stats.c          | 16 +++---
src/backend/statistics/mcv.c                     | 62 +++++++-----------------
src/include/statistics/extended_stats_internal.h |  2 +-
3 files changed, 26 insertions(+), 54 deletions(-)


pgsql-committers by date:

Previous
From: Tomas Vondra
Date:
Subject: pgsql: Rework examine_opclause_expression to use varonleft
Next
From: Peter Geoghegan
Date:
Subject: pgsql: Don't rely on estimates for amcheck Bloom filters.