From 21995d3f6d69670b5bc5b3654970701f8abb6d9f Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 1 Oct 2015 10:31:22 -0400 Subject: [PATCH] Fix documentation error in commit 8703059c6b55c427100e00a09f66534b6ccbfaa1. Etsuro Fujita spotted a thinko in the README commentary. --- src/backend/optimizer/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/backend/optimizer/README b/src/backend/optimizer/README index 1140e02e474..916a51852e3 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.