3 ms·
I think IVFFlat and HNSW are very different implementations. So we would be forcing a choice for a pgvector user of what index to use. Our on disk path will re
by nikita 3y ago
I think IVFFlat and HNSW are very different implementations. So we would be forcing a choice for a pgvector user of what index to use.
Our on disk path will require us to run a number of experiments with the storage format. We will move faster with a separate project.
Medium to long term we are very open to merge them.
- kiwicopple 3y agoThey are different, but that doesn't preclude pgvector supporting both indexes. I get that it's slower to take a collaborative approach - but that's part of open source. > will require us to run a number of experiments with the storage format I'd personally consider this a feature, if you want to maintain Postgres compatibility and allow your users to migrate in/out easily