From: Michael Paquier Date: Tue, 6 Jan 2026 03:30:01 +0000 (+0900) Subject: Fix typo in planner.c X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ae283736025c2d0b41a4106788b4e45ffba6c82d;p=thirdparty%2Fpostgresql.git Fix typo in planner.c b8cfcb9e00da did not get this change right. Author: Alexander Law Discussion: https://postgr.es/m/CAJ0YPFFWhJXs-e-=7iJz-FLp=b1dXfJA_qtrVAgto=bZmzD9zQ@mail.gmail.com --- diff --git a/src/backend/optimizer/plan/planner.c b/src/backend/optimizer/plan/planner.c index da6e7fd34b0..7a6b8b749f2 100644 --- a/src/backend/optimizer/plan/planner.c +++ b/src/backend/optimizer/plan/planner.c @@ -7922,8 +7922,8 @@ apply_scanjoin_target_to_paths(PlannerInfo *root, * However, there are several cases when this optimization is not safe. If * the rel isn't partitioned, then none of the paths will be Append or * MergeAppend paths, so we should definitely not do this. If it is - * partititoned but is a joinrel, it may have Append and MergeAppend - * paths, but it can also have join paths that we can't afford to discard. + * partitioned but is a joinrel, it may have Append and MergeAppend paths, + * but it can also have join paths that we can't afford to discard. * * Some care is needed, because we have to allow * generate_useful_gather_paths to see the old partial paths in the next