-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connect using Connection Service File #87
Connect using Connection Service File #87
Conversation
For those who already have their Connection Service Files setup, it is useful not to have to specify the configuration file. By connection using the service=<name> format we delegate all the resolving of service file locations to libpq.
It breaks the functionality of picking up a specific instance among the auto-detected one, i.e. perhaps you have 3 clusters With the proposed changes it will complain if there is no record for A in I'd propose adding some other parameter to point specifically to a service record. Also, we probably want to give priority to the case where the option.host is set, as it is more specific than the name of the service (line 210 should be swapped with line 207). |
Avoid using the same value under different names. Avoid unnecessary abbreviations
What about introducing another flag to specify the service?
|
Connection service file edits
I've used exactly |
I pulled in those changes into this PR. |
👍 |
1 similar comment
👍 |
Thanks @feikesteenbergen |
For those who already have their Connection Service Files setup, it is
useful not to have
to specify the configuration file.
By connection using the service= format we delegate all the
resolving of service file
locations to libpq.
Requires issue #85 to be fixed.