|
26 | 26 | *typing strategy by changing hash function.
|
27 | 27 | * 2. New query type proceeding. The handling policy for new query types is
|
28 | 28 | *contained in variable 'aqo.mode'. It accepts three values:
|
29 |
| - *"intelligent", "forced", and "manual". |
| 29 | + *"intelligent", "forced","controlled"and "disabled". |
30 | 30 | *Intelligent linking strategy means that for each new query type the new
|
31 | 31 | *separate feature space is created. The hash of new feature space is
|
32 | 32 | *set the same as the hash of new query type. Auto tuning is on by
|
|
35 | 35 | *Forced linking strategy means that every new query type is linked to
|
36 | 36 | *the common feature space with hash 0, but we don't memorize
|
37 | 37 | *the hash and the settings for this query.
|
38 |
| - *Manual linking strategy means that new query types do not induce new |
39 |
| - *feature spaces neither interact AQO somehow. In this mode the |
| 38 | + *Controlled linking strategy means that new query types do not induce |
| 39 | + *newfeature spaces neither interact AQO somehow. In this mode the |
40 | 40 | *configuration of settings for different query types lies completely on
|
41 | 41 | *user.
|
| 42 | + *Disabled strategy means that AQO is disabled for all queries. |
42 | 43 | * 3. For given query type we determine its query_hash, use_aqo, learn_aqo,
|
43 | 44 | *fspace_hash and auto_tuning parameters.
|
44 | 45 | * 4. For given fspace_hash we may use its machine learning settings, but now
|
@@ -145,7 +146,7 @@ aqo_planner(Query *parse,
|
145 | 146 | fspace_hash=0;
|
146 | 147 | collect_stat= false;
|
147 | 148 | break;
|
148 |
| -caseAQO_MODE_MANUAL: |
| 149 | +caseAQO_MODE_CONTROLLED: |
149 | 150 | adding_query= false;
|
150 | 151 | learn_aqo= false;
|
151 | 152 | use_aqo= false;
|
|