Use /etc/hosts for postgres internal DNS resolving #1195
Merged
Conversation
This file contains 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
furkansahin
approved these changes
Feb 6, 2024
|
I like this and it's alright to merge it. However, soon, after this PR #1196, we may also start configuring dnsmasq for these operations. This way, we will also be able to assign private hostnames. |
byucesoy
force-pushed
the
pg-etc-host
branch
from
80d5b96
to
393cbe4
Compare
This has 3 primary benefits; - It is faster than making DNS queries - It is faster and swift (no TTL) to update - It allows setting up standbys that uses fully qualified domain names even when there is no DNS server (i.e. development environments)
byucesoy
force-pushed
the
pg-etc-host
branch
from
393cbe4
to
b880206
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This has 3 primary benefits;