René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"PostgreSQL online store ignores database search_path, breaking extensions like pgvector","articleBody":"## Expected Behavior\n\n  When vector_enabled: true is configured and the pgvector extension is installed in the database (in public schema), Feast should be able to create tables with vector columns. The database's configured search_path should be respected.\n\n## Current Behavior\n\n  Feast fails with psycopg.errors.UndefinedObject: type \"vector\" does not exist because it hardcodes the connection search_path to only the db_schema value, excluding public where extensions are typically installed:\n```\n # feast/infra/utils/postgres/connection_utils.py#L76\n  \"options\": \"-c search_path={}\".format(config.db_schema or config.user),\n```\n  This overrides any database or user-level search_path settings.\n\n  Steps to Reproduce\n\n  1. Install pgvector extension in PostgreSQL:\n  CREATE EXTENSION vector;  -- installs to public by default\n  2. Configure feature_store.yaml with a custom schema:\n  online_store:\n    type: postgres\n    db_schema: feast_online\n    vector_enabled: true\n  3. Run feast apply\n  4. Error occurs:\n  psycopg.errors.UndefinedObject: type \"vector\" does not exist\n  LINE 8:                             vector_value vector NULL,\n\n  ## Specifications\n\n  - Version: 0.58.0\n  - Platform: macOS / Linux\n  - Subsystem: PostgreSQL\n","author":{"url":"https://github.com/max36067","@type":"Person","name":"max36067"},"datePublished":"2026-01-05T09:39:49.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/5814/feast/issues/5814"}