supabase/supavisor

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

Open

#343 opened on May 28, 2024

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Elixir (2,191 stars) (106 forks)batch import
enhancementgood first issue

Description

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

Contributor guide

Tech stack
elixirpostgresql
Domain
backenddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Elixir basicsUnderstanding of Postgres connection poolingFamiliarity with Supavisor architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
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.