Enable partitioning for knowledge-bases to support multi-tenancy properly

[vizsatiz]

For applications with multiple tenants, sharing an approximate index between tenants means vectors from one tenant can affect recall (and speed) for other tenants.

For tenant isolation, use list partitioning or separate tables.

CREATE TABLE items (customer_id int, embedding vector(3)) PARTITION BY LIST(customer_id);

https://github.com/pgvector/pgvector#multitenancy