supabase/supavisor

Connection Pooler string does not honor options parameter with search_path

Open

#206 建立於 2023年11月24日

在 GitHub 查看
 (4 留言) (10 反應) (0 負責人)Elixir (2,191 star) (106 fork)batch import
buggood first issue

描述

Bug report

  • [ x] I confirm this is a bug with Supabase, not with my own application.
  • [ x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Postgres connection strings support an options query parameter where one can add a specific search_path to be used for the connection:

POSTGRES_CONNECTION_STRING?options=-c%20search_path=custom_schema

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.

貢獻者指南

技術棧
elixirpostgresql
領域
databasebackend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of PostgreSQLFamiliarity with Elixir codebase
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
45
研究方向
Investigate how supavisor parses the connection string and handles query parameters. Focus on the parsing logic where options like 'search path' are passed via the 'options' parameter. Compare with direct connection handling. Look in the connection pooler code for filtering or omitting parameters. Check if there's a need to forward the 'options' parameter to the backend connection. The relevant files are likely in the pool handling or connection configuration modules. Review issue comments for any additional hints.