Don't fail if the application_name is not set properly
Open
- Dominant language
- Perl
- Stars
- 350
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
If you set application_name to a wrong value, pgsqlms returns a "OCF_ERR_CONFIGURED" that will trigger fencing of the nodes where the service are started. It should return "OCF_ERR_ARGS" instead.
pgsqlms should return a lower level error.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating pgsqlms handling for an invalid application_name and the mapping of its OCF error codes. Reproduce the wrong-value case, then verify that it returns OCF_ERR_ARGS rather than OCF_ERR_CONFIGURED, so the error does not trigger node fencing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100