supabase/supavisor

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

Open

Aperta il 28 mag 2024

Vedi su GitHub
 (4 commenti) (0 reazioni) (0 assegnatari)Elixir (2191 star) (106 fork)batch import
enhancementgood first issue

Descrizione

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

Guida contributor

Tech stack
elixirpostgresql
Dominio
backenddatabase
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-2 days
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Elixir basicsUnderstanding of Postgres connection poolingFamiliarity with Supavisor architecture
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
35
Direzione di ricerca
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.