diff options
| author | Tom Lane | 2015-10-01 14:31:22 +0000 |
|---|---|---|
| committer | Tom Lane | 2015-10-01 14:32:13 +0000 |
| commit | 1128b7735dd23dc9dedf034f7e8236d84f22fd51 (patch) | |
| tree | ddc287c0c5f8eb10c5c71b9a388fbf87800a749b | |
| parent | 5091f39afe7fef1cccaf501d3c5dd1ec847c7f97 (diff) | |
Fix documentation error in commit 8703059c6b55c427100e00a09f66534b6ccbfaa1.
Etsuro Fujita spotted a thinko in the README commentary.
| -rw-r--r-- | src/backend/optimizer/README | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/optimizer/README b/src/backend/optimizer/README index d63e95850a7..7cdc239186f 100644 --- a/src/backend/optimizer/README +++ b/src/backend/optimizer/README @@ -254,7 +254,7 @@ lower leftjoin has min LHS of {B} and min RHS of {C,D}. Given such information, join_is_legal would think it's okay to associate the upper join into the lower join's RHS, transforming the query to B leftjoin (A leftjoin (C innerjoin D) on Pa) on (Pbcd) -which yields totally wrong answers. We prevent that by forcing the min LHS +which yields totally wrong answers. We prevent that by forcing the min RHS for the upper join to include B. This is perhaps overly restrictive, but such cases don't arise often so it's not clear that it's worth developing a more complicated system. |