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
@Drzhivago264 Instinctively, I would say that your WHERE condition isn't going to use the PGVectorSpace DiskANN index and will have to scan the entire table to find the matching rows.
There might be an index on dataset_id which could pre-filter the rows but that would unrelated to the vectors.
@cevian I can confirm that this could be very handy indeed. We have a few uses cases where the number of results is undefined and all matching results within a certain distance or similarity should be returned.
We currently have not found a great solution for this.
Right now we only support ORDER BY distance queries. We should add support for WHERE distance <0.6 queries too.
The text was updated successfully, but these errors were encountered: