diff options
| author | Peter Eisentraut | 2016-07-15 02:48:26 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2016-07-15 02:48:26 +0000 |
| commit | 63cfdb8dde7f25a095af03aa204580fea55c6c07 (patch) | |
| tree | a2c2a7a210f6294beec1ff5cefc3863b743252ff /src/backend/optimizer | |
| parent | 3aed52a622b1c83abc45c6a7c0ef6dbb9adaa7e1 (diff) | |
Adjust spellings of forms of "cancel"
Diffstat (limited to 'src/backend/optimizer')
| -rw-r--r-- | src/backend/optimizer/util/orclauses.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/optimizer/util/orclauses.c b/src/backend/optimizer/util/orclauses.c index ea831f5a82..13570f006e 100644 --- a/src/backend/optimizer/util/orclauses.c +++ b/src/backend/optimizer/util/orclauses.c @@ -54,7 +54,7 @@ static void consider_new_or_clause(PlannerInfo *root, RelOptInfo *rel, * fault is not really in the transformation, but in clauselist_selectivity's * inability to recognize redundant conditions.) We can compensate for this * redundancy by changing the cached selectivity of the original OR clause, - * cancelling out the (valid) reduction in the estimated sizes of the base + * canceling out the (valid) reduction in the estimated sizes of the base * relations so that the estimated joinrel size remains the same. This is * a MAJOR HACK: it depends on the fact that clause selectivities are cached * and on the fact that the same RestrictInfo node will appear in every |