mirror of
https://github.com/pgvector/pgvector.git
synced 2026-07-12 15:46:54 +08:00
Moved FAQ [skip ci]
This commit is contained in:
16
README.md
16
README.md
@@ -414,14 +414,6 @@ Yes, pgvector uses the write-ahead log (WAL), which allows for replication and p
|
|||||||
|
|
||||||
You’ll need to use [dimensionality reduction](https://en.wikipedia.org/wiki/Dimensionality_reduction) at the moment.
|
You’ll need to use [dimensionality reduction](https://en.wikipedia.org/wiki/Dimensionality_reduction) at the moment.
|
||||||
|
|
||||||
#### Do indexes need to fit into memory?
|
|
||||||
|
|
||||||
No, but as with other index types, you’ll likely see better performance if they do. You can get the size of an index with:
|
|
||||||
|
|
||||||
```sql
|
|
||||||
SELECT pg_size_pretty(pg_relation_size('index_name'));
|
|
||||||
```
|
|
||||||
|
|
||||||
#### Can I store vectors with different dimensions in the same column?
|
#### Can I store vectors with different dimensions in the same column?
|
||||||
|
|
||||||
You can use `vector` as the type (instead of `vector(3)`).
|
You can use `vector` as the type (instead of `vector(3)`).
|
||||||
@@ -471,6 +463,14 @@ and query with:
|
|||||||
SELECT * FROM items ORDER BY embedding::vector(3) <-> '[3,1,2]' LIMIT 5;
|
SELECT * FROM items ORDER BY embedding::vector(3) <-> '[3,1,2]' LIMIT 5;
|
||||||
```
|
```
|
||||||
|
|
||||||
|
#### Do indexes need to fit into memory?
|
||||||
|
|
||||||
|
No, but like other index types, you’ll likely see better performance if they do. You can get the size of an index with:
|
||||||
|
|
||||||
|
```sql
|
||||||
|
SELECT pg_size_pretty(pg_relation_size('index_name'));
|
||||||
|
```
|
||||||
|
|
||||||
## Troubleshooting
|
## Troubleshooting
|
||||||
|
|
||||||
#### Why isn’t a query using an index?
|
#### Why isn’t a query using an index?
|
||||||
|
|||||||
Reference in New Issue
Block a user