0003-Comment-on-restriction-of-OR-SAOP-element-type.patch
text/x-patch
Filename: 0003-Comment-on-restriction-of-OR-SAOP-element-type.patch
Type: text/x-patch
Part: 2
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: format-patch
Series: patch 0003
Subject: Comment on restriction of OR->SAOP element type
| File | + | − |
|---|---|---|
| src/backend/optimizer/path/indxpath.c | 4 | 1 |
From fabb970f0acdb1bb3b7280f05ffce9facf89af44 Mon Sep 17 00:00:00 2001 From: "Andrei V. Lepikhov" <lepihov@gmail.com> Date: Wed, 9 Oct 2024 16:17:27 +0700 Subject: [PATCH 3/3] Comment on restriction of OR->SAOP element type --- src/backend/optimizer/path/indxpath.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/backend/optimizer/path/indxpath.c b/src/backend/optimizer/path/indxpath.c index a2ddfb2bb9..c8625a32d4 100644 --- a/src/backend/optimizer/path/indxpath.c +++ b/src/backend/optimizer/path/indxpath.c @@ -2538,7 +2538,10 @@ match_clause_to_index(PlannerInfo *root, * (3) must match the collation of the index, if collation is relevant. * * Our definition of "const" is exceedingly liberal: we allow anything that - * doesn't involve a volatile function or a Var of the index's relation. + * doesn't involve a volatile function or a Var of the index's relation + * except for a boolean OR expression input: due to trade-off between + * expected execution speedup planning complexity, we limit or->saop + * transformation by obvious cases when an index scan can get a profit. * In particular, Vars belonging to other relations of the query are * accepted here, since a clause of that form can be used in a * parameterized indexscan. It's the responsibility of higher code levels -- 2.39.5