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
This works if I use the direct Postgres connection string shown on the Supabase dashboard but does not work with the connection pooler string (Supavisor). Is this by design? I ran multiple tests and the search path in my connection only updates when I use the direct connection string.
Expected behavior
The search path to be set as specified in the additional parameters passed to the connection pooler string.
Additional context
I am using the connection pooler in Transaction mode.
The text was updated successfully, but these errors were encountered:
Bug report
Describe the bug
Postgres connection strings support an
options
query parameter where one can add a specificsearch_path
to be used for the connection:This works if I use the direct Postgres connection string shown on the Supabase dashboard but does not work with the connection pooler string (Supavisor). Is this by design? I ran multiple tests and the search path in my connection only updates when I use the direct connection string.
Expected behavior
The search path to be set as specified in the additional parameters passed to the connection pooler string.
Additional context
I am using the connection pooler in Transaction mode.
The text was updated successfully, but these errors were encountered: