Juan José Mata 30ef253536 Fix pgvector migration to only run when explicitly configured (#1239) ...

The migration previously checked only if the pgvector extension was
available on the PostgreSQL server. In production Docker environments
(e.g., managed Postgres services), the extension may be present but the
database user lacks superuser privileges to enable it, causing the
migration to fail.

Now the migration requires VECTOR_STORE_PROVIDER=pgvector to be set
before attempting to enable the extension, matching the application's
own configuration pattern in VectorStore::Registry.

https://claude.ai/code/session_017YYBFXGwamXpGwwDZxe8Pv

Co-authored-by: Claude <noreply@anthropic.com>

2026-03-21 09:24:11 +01:00

..

eval_data

Small llms improvements (#400)

2025-12-07 18:11:34 +01:00

migrate

Fix pgvector migration to only run when explicitly configured (#1239)

2026-03-21 09:24:11 +01:00

seeds

Add Google Sign-In (SSO) support to Flutter mobile app (#860)

2026-02-06 00:45:11 +01:00

schema.rb

Initial split transaction support (#1230)

2026-03-20 21:19:30 +01:00

seeds.rb

Benchmarking setup (#2366)

2025-06-14 11:53:53 -04:00