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
"While we recommend the timescale-vector index type, we also have 2 more index types availabe:\n",
534
-
"- The pgvector ivfflat index\n",
535
-
"- The pgvector hnsw index\n",
535
+
"\n",
536
+
"* The pgvector ivfflat index\n",
537
+
"* The pgvector hnsw index\n",
536
538
"\n",
537
539
"Usage examples below:"
538
540
]
@@ -577,9 +579,10 @@
577
579
"Yet, traditionally, searching by two components \"similarity\" and \"time\" is challenging approximate nearest neigbor (ANN) indexes and makes the similariy-search index less effective.\n",
578
580
"\n",
579
581
"One approach to solving this is partitioning the data by time and creating ANN indexes on each partition individually. Then, during search you can:\n",
580
-
"- Step 1: filter our partitions that don't match the time predicate\n",
581
-
"- Step 2: perform the similarity search on all matching partitions\n",
582
-
"- Step 3: combine all the results from each partition in step 2, rerank, and filter out results by time.\n",
582
+
"\n",
583
+
" * Step 1: filter our partitions that don't match the time predicate\n",
584
+
" * Step 2: perform the similarity search on all matching partitions\n",
585
+
" * Step 3: combine all the results from each partition in step 2, rerank, and filter out results by time.\n",
583
586
"\n",
584
587
"Step 1 makes the search a lot more effecient by filtering out whole swaths of data in one go.\n",
0 commit comments