wdevs/relspecgo
5
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Releases 46 Wiki Activity

Set postgres application_name when connecting #3

New Issue
Open
opened 2026-04-15 22:22:50 +00:00 by sgcommand · 1 comment
sgcommand commented 2026-04-15 22:22:50 +00:00
Member
Copy Link

Set the PostgreSQL application_name when opening database connections so sessions are identifiable in pg_stat_activity and monitoring.

Why:

  • easier to trace which service opened a connection
  • better observability during debugging and performance analysis
  • clearer separation of relspecgo traffic from other clients

Suggested implementation:

  • set application_name explicitly in the PostgreSQL DSN or client config
  • use a stable value like relspecgo, or a more specific component name if needed

Acceptance criteria:

  • new PostgreSQL connections from relspecgo include application_name
  • the value is visible in pg_stat_activity
  • documentation and/or tests updated where practical
Set the PostgreSQL application_name when opening database connections so sessions are identifiable in pg_stat_activity and monitoring. Why: - easier to trace which service opened a connection - better observability during debugging and performance analysis - clearer separation of relspecgo traffic from other clients Suggested implementation: - set application_name explicitly in the PostgreSQL DSN or client config - use a stable value like relspecgo, or a more specific component name if needed Acceptance criteria: - new PostgreSQL connections from relspecgo include application_name - the value is visible in pg_stat_activity - documentation and/or tests updated where practical
sgcommand commented 2026-04-15 22:31:34 +00:00
Author
Member
Copy Link

Also include the application version in the PostgreSQL application_name value if practical, so connections are attributable to both the service and the running build version. For example: relspecgo/1.2.3 or similar. This would make it easier to correlate behavior with deployments and identify which version opened a given session in pg_stat_activity.

Also include the application version in the PostgreSQL application_name value if practical, so connections are attributable to both the service and the running build version. For example: relspecgo/1.2.3 or similar. This would make it easier to correlate behavior with deployments and identify which version opened a given session in pg_stat_activity.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
hein root sam sgcommand warkanum
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/relspecgo#3
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?