Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 23ef119

Browse files
committed
Revise the header comment for match_clause_to_indexcol()
Since d4378c0, match_clause_to_indexcol() doesn't always return NULL for an OR clause. This commit reflects that in the function header comment. Reported-by: Pavel Borisov <pashkin.elfe@gmail.com>
1 parent f3e4aeb commit 23ef119

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

src/backend/optimizer/path/indxpath.c

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2639,8 +2639,9 @@ match_clause_to_index(PlannerInfo *root,
26392639
* Returns an IndexClause if the clause can be used with this index key,
26402640
* or NULL if not.
26412641
*
2642-
* NOTE: returns NULL if clause is an OR or AND clause; it is the
2643-
* responsibility of higher-level routines to cope with those.
2642+
* NOTE: This routine always returns NULL if the clause is an AND clause.
2643+
* Higher-level routines deal with OR and AND clauses. OR clause can be
2644+
* matched as a whole by match_orclause_to_indexcol() though.
26442645
*/
26452646
static IndexClause *
26462647
match_clause_to_indexcol(PlannerInfo *root,

0 commit comments

Comments
 (0)