address more reviewer comments

Author: taroface

src/current/_includes/v25.2/known-limitations/vector-limitations.md

@@ -5,4 +5,4 @@
 - Index acceleration with filters is only supported if the filters match prefix columns. [#146145](https://github.com/cockroachdb/cockroach/issues/146145)
 - Index recommendations are not provided for vector indexes. [#146146](https://github.com/cockroachdb/cockroach/issues/146146)
 - Vector index queries may return incorrect results when the underlying table uses multiple column families. [#146046](https://github.com/cockroachdb/cockroach/issues/146046)
-- Queries may ignore filter conditions (e.g., a `WHERE` clause) when multiple vector indexes exist on the same `VECTOR` column, and one has a prefix column. [#146257](https://github.com/cockroachdb/cockroach/issues/146257)
+- Queries against a vector index may ignore filter conditions (e.g., a `WHERE` clause) when multiple vector indexes exist on the same `VECTOR` column, and one has a prefix column. [#146257](https://github.com/cockroachdb/cockroach/issues/146257)

src/current/_includes/v25.2/sql/vector-batch-inserts.md

@@ -1 +1 @@
-Large batch inserts of [`VECTOR`]({% link {{ page.version.version }}/vector.md %}) types can cause performance degradation. When inserting vectors, batching should be avoided.
+Large batch inserts of [`VECTOR`]({% link {{ page.version.version }}/vector.md %}) types can cause performance degradation. When inserting vectors, batching should be avoided. For an example, refer to [Create and query a vector index]({% link {{ page.version.version }}/vector-indexes.md %}#create-and-query-a-vector-index).

src/current/v25.2/create-index.md

@@ -48,7 +48,7 @@ Parameter | Description
 `IF NOT EXISTS` | Create a new index only if an index of the same name does not already exist; if one does exist, do not return an error.
 `opt_index_name`<br>`index_name` | The name of the index to create, which must be unique to its table and follow these [identifier rules]({% link {{ page.version.version }}/keywords-and-identifiers.md %}#identifiers).<br><br>If you do not specify a name, CockroachDB uses the format `<table>_<columns>_key/idx`. `key` indicates the index applies the `UNIQUE` constraint; `idx` indicates it does not. Example: `accounts_balance_idx`
 `table_name` | The name of the table you want to create the index on.
-`USING name` | An optional clause for compatibility with third-party tools. Accepted values for `name` are `btree`, `gin`, and `gist`, with `btree` for a standard secondary index, `gin` as the PostgreSQL-compatible syntax for a [GIN index](#create-gin-indexes), `gist` for a [spatial index]({% link {{ page.version.version }}/spatial-indexes.md %}), and `cspann` for a [vector index]({% link {{ page.version.version }}/vector-indexes.md %}). `hnsw` and `ivfflat` are aliased to `cspann` for compatibility with [`pgvector`](https://github.com/pgvector/pgvector) syntax.
+`USING name` | An optional clause for compatibility with third-party tools. Accepted values for `name` are `btree`, `gin`, and `gist`, with `btree` for a standard secondary index, `gin` as the PostgreSQL-compatible syntax for a [GIN index](#create-gin-indexes), `gist` for a [spatial index]({% link {{ page.version.version }}/spatial-indexes.md %}), and `cspann` for a [vector index]({% link {{ page.version.version }}/vector-indexes.md %}). `hnsw` is aliased to `cspann` for compatibility with [`pgvector`](https://github.com/pgvector/pgvector) syntax.
 `name` | The name of the column you want to index. For [multi-region tables]({% link {{ page.version.version }}/multiregion-overview.md %}#table-localities), you can use the `crdb_region` column within the index in the event the original index may contain non-unique entries across multiple, unique regions.
 `ASC` or `DESC`| Sort the column in ascending (`ASC`) or descending (`DESC`) order in the index. How columns are sorted affects query results, particularly when using `LIMIT`.<br><br>__Default:__ `ASC`
 `STORING ...`| Store (but do not sort) each column whose name you include.<br><br>For information on when to use `STORING`, see  [Store Columns](#store-columns).  Note that columns that are part of a table's [`PRIMARY KEY`]({% link {{ page.version.version }}/primary-key.md %}) cannot be specified as `STORING` columns in secondary indexes on the table.<br><br>`COVERING` and `INCLUDE` are aliases for `STORING` and work identically.

src/current/v25.2/vector-indexes.md

@@ -58,29 +58,59 @@ You can also specify a vector index during table creation. For example:
 {% include_cached copy-clipboard.html %}
 ~~~ sql
 CREATE TABLE items (
-    category STRING,
+    department_id INT,
+    category_id INT,
     embedding VECTOR(1536),
     VECTOR INDEX (embedding)
 );
 ~~~
 
-You can create a vector index with a *prefix column* to pre-filter the search space. This is especially useful for tables containing millions of vectors or more. For an example, refer to [Create and query a vector index](#create-and-query-a-vector-index).
+### Prefix columns
+
+You can create a vector index with one or more *prefix columns* to pre-filter the search space. This is especially useful for tables containing millions of vectors or more. 
 
 {% include_cached copy-clipboard.html %}
 ~~~ sql
 CREATE TABLE items (
-    category STRING,
+    department_id INT,
+    category_id INT,
     embedding VECTOR(1536),
-    VECTOR INDEX (category, embedding)
+    VECTOR INDEX (department_id, category_id, embedding)
 );
 ~~~
 
+A vector index is only used if each prefix column is constrained to a specific value in the query. For example:
+
+{% include_cached copy-clipboard.html %}
+~~~ sql
+WHERE department_id = 100 AND category_id = 200
+~~~
+
+You can filter on multiple prefix values using `IN`:
+
+{% include_cached copy-clipboard.html %}
+~~~ sql
+WHERE (department_id, category_id) IN ((100, 200), (300, 400))
+~~~
+
+The following example will not use the vector index:
+
+{% include_cached copy-clipboard.html %}
+~~~ sql
+WHERE department_id = 100 AND category_id >= 200
+~~~
+
+For an example, refer to [Create and query a vector index](#create-and-query-a-vector-index).
+
+### Vector index opclass
+
 You can optionally specify an opclass. If not specified, the default is `vector_l2_ops`:
 
 {% include_cached copy-clipboard.html %}
 ~~~ sql
 CREATE TABLE items (
-    category STRING,
+    department_id INT,
+    category_id INT,
     embedding VECTOR(1536),
     VECTOR INDEX embed_idx (embedding vector_l2_ops)
 );
@@ -199,23 +229,18 @@ In the following example, a vector index with a prefix column is used to optimiz
     --http-addr=localhost:8080
     ~~~
 
-1. In a separate terminal, [enable vector indexes](#enable-vector-indexes) on the cluster and session:
-
-    {% include_cached copy-clipboard.html %}
-    ~~~ sql
-    SET CLUSTER SETTING feature.vector_index.enabled = true;
-    ~~~
+1. In a separate terminal, open a SQL shell on the cluster:
 
     {% include_cached copy-clipboard.html %}
-    ~~~ sql
-    SET sql_safe_updates = false;
+    ~~~ shell
+    cockroach sql --insecure
     ~~~
 
-1. Open a SQL shell on the cluster:
+1. [Enable vector indexes](#enable-vector-indexes) on the cluster:
 
     {% include_cached copy-clipboard.html %}
-    ~~~ shell
-    cockroach sql --insecure
+    ~~~ sql
+    SET CLUSTER SETTING feature.vector_index.enabled = true;
     ~~~
 
 1. Create an `items` table that includes a `VECTOR` column called `embedding`, along with a vector index that uses `customer_id` as the prefix column:
@@ -238,7 +263,7 @@ In the following example, a vector index with a prefix column is used to optimiz
     python fast_insert.py
     ~~~
 
-    This process should take approximately 20 minutes.
+    This process should take approximately 5-10 minutes.
 
 1. When the script is finished executing, verify that `items` is populated: