aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlexander Korotkov <akorotkov@postgresql.org>2025-02-04 23:18:47 +0200
committerAlexander Korotkov <akorotkov@postgresql.org>2025-02-04 23:18:47 +0200
commit23ef119f58e3eaa29bedc69320fd61b108ab8c10 (patch)
tree28d29ef75adfbcec52d87aedba93053df25c6b41
parentf3e4aeb744da6acf909e9c5a7a83338fba1984a7 (diff)
downloadpostgresql-23ef119f58e3eaa29bedc69320fd61b108ab8c10.tar.gz
postgresql-23ef119f58e3eaa29bedc69320fd61b108ab8c10.zip
Revise the header comment for match_clause_to_indexcol()
Since d4378c0005e6, 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>
-rw-r--r--src/backend/optimizer/path/indxpath.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/src/backend/optimizer/path/indxpath.c b/src/backend/optimizer/path/indxpath.c
index fa3edf60f3c..a58cf5bad1a 100644
--- a/src/backend/optimizer/path/indxpath.c
+++ b/src/backend/optimizer/path/indxpath.c
@@ -2639,8 +2639,9 @@ match_clause_to_index(PlannerInfo *root,
* Returns an IndexClause if the clause can be used with this index key,
* or NULL if not.
*
- * NOTE: returns NULL if clause is an OR or AND clause; it is the
- * responsibility of higher-level routines to cope with those.
+ * NOTE: This routine always returns NULL if the clause is an AND clause.
+ * Higher-level routines deal with OR and AND clauses. OR clause can be
+ * matched as a whole by match_orclause_to_indexcol() though.
*/
static IndexClause *
match_clause_to_indexcol(PlannerInfo *root,