Support for PostgreSQL Application Name Connection Options

Bug #1492793 reported by Jason Boyer on 2015-09-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Wishlist
Unassigned

Bug Description

There is a libpq option to set the application name for the connection that we're not currently taking advantage of. I've got a branch that adds this support for the application_name database parameter. For logging assistance you could add the name of your app servers to the beginning or end of the service name.

Jason Boyer (jboyer) on 2016-01-19
tags: added: pullrequest
Galen Charlton (gmc) wrote :

The branch user/gmcharlt/lp1492793_pg_app_name contains a signed-off version of Jason's patch as well as two follow-ups:

- teaching Clark Kent how to set the application name
- adding release notes

  http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/lp1492793_pg_app_name

Changed in evergreen:
milestone: 2.next → 2.10-beta
status: New → Confirmed
tags: added: signedoff
Galen Charlton (gmc) wrote :

No additional live tests are included, intentionally, as an issue with this feature would almost certainly manifest itself pretty clearly as an inability to connect to the database.

Mike Rylander (mrylander) wrote :

Merged to master for 2.10 goodness. Thanks, Jason and Galen!

Changed in evergreen:
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers