The community member's post discusses a version conflict between the llama-index-vector-stores-postgres package and the pgvector package. The llama-index-vector-stores-postgres package constrains its pgvector version to <0.3.0, but pgvector is now on version 0.3.2. The community member is currently pinning to version 0.2.5 of pgvector, but suggests it would be good to increment the version to avoid disrupting the onboarding flow.
In the comments, another community member agrees that the constraint could be easily updated to be less strict.
version conflict: llama-index-vector-stores-postgres constrains its pgvector version to <0.3.0. But pgvector is now on version 0.3.2 -- pinning to 0.2.5 for now but would be good to increment since it disrupts onboarding flow
