You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: allow user to set vbase range
Signed-off-by: silver-ymz <[email protected]>
* separate the enable_vbase and vbase_range settings
Signed-off-by: silver-ymz <[email protected]>
---------
Signed-off-by: silver-ymz <[email protected]>
Copy file name to clipboardExpand all lines: docs/searching.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,7 @@ Search options are specified by PostgreSQL GUC. You can use `SET` command to app
31
31
| vectors.k | integer | Expected number of candidates returned by index. The parameter will influence the recall if you use HNSW or quantization for indexing. Default value is `64`. |
32
32
| vectors.enable_prefilter | boolean | Enable prefiltering or not. Default value is `off`. |
33
33
| vectors.enable_vector_index | boolean | Enable vector indexes or not. This option is for debugging. Default value is `on`. |
34
-
| vectors.enable_vbase | boolean | Enable vbase optimization. Default value is `off`. |
34
+
| vectors.enable_vbase | boolean | Enable vbase optimization or not. Default value is `off`. |
35
+
| vectors.vbase_range | integer | Range size of vbase optimization. The larger the range, the more accurate the result, but the slower the speed. Default value is `100`. |
35
36
36
37
Note: When `vectors.enable_vbase` is enabled, prefilter does not work.
0 commit comments