supabase/supavisor

Prepend application_name from client to application_name set by DbHandler only in session mode

Open

#343 建立於 2024年5月28日

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

描述

When looking at connections in Postgres I should be able to see the application_name set by clients if connected via session mode through Supavisor.

select usename, application_name from pg_stat_activity;

application_name should be my_special_application_name via Supavisor

貢獻者指南

技術棧
elixirpostgresql
領域
backenddatabase
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Elixir basicsUnderstanding of Postgres connection poolingFamiliarity with Supavisor architecture
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
The issue requires modifying session mode handling to prepend the client's application name to the one set by DbHandler. Investigate how application name is currently set in the DbHandler module and in the session proxy. Look for where connection parameters are passed and concatenated. The solution likely involves editing the session initialization code to combine the client provided application name with the existing one, separated by ' via '. Check existing tests for session mode to ensure no regressions.