You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b472355
Browse filesBrowse the repository at this point in the historyBrowse files
π fix: require USAGE/CREATE privileges on POSTGRES_SCHEMA
Schema-existence alone doesn't guarantee the app role can actually
create or read from it β a role with USAGE but no CREATE on `myapp`,
and CREATE on `public`, would still have pgvector tables silently land
in `public` because `_build_search_path` appends `public` as a fallback
for vector-type resolution.
Check has_schema_privilege('USAGE') and has_schema_privilege('CREATE')
for each requested schema via a single query, and raise a combined
error listing exactly which schemas are missing vs. which lack which
grant so operators know what to fix.
0 commit comments