Tag connections with application_name#2958
Merged
Merged
Conversation
Set application_name on every Postgres connection so each session is identifiable in pg_stat_activity. No behaviour change. Naming: - Shared Knex pool: odota-<APP_NAME> - runReliableQueue dedicated Client: odota-<APP_NAME>-queue - Explorer readonly Pool: odota-<APP_NAME>-explorer - archivePostgresStream Client: odota-<APP_NAME>-archive APP_NAME is set per process by ecosystem.config.js (e.g. inserter, scanner, web, parser); falls back to "unknown" when run outside PM2. With ~30 backend roles plus a clustered web role, this makes it possible to answer "which service is holding connections?" with a single query: SELECT application_name, state, count(*) FROM pg_stat_activity GROUP BY 1, 2 ORDER BY 3 DESC; Co-authored-by: Cursor <cursoragent@cursor.com>
howardchung
approved these changes
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Set application_name on every Postgres connection so each session is
identifiable in pg_stat_activity. No behaviour change.
Naming:
APP_NAME is set per process by ecosystem.config.js (e.g. inserter,
scanner, web, parser); falls back to "unknown" when run outside PM2.
With ~30 backend roles plus a clustered web role, this makes it possible
to answer "which service is holding connections?" with a single query: