Skip to content
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

fix(postgres): empty socketDir by default #160

Merged
merged 3 commits into from
Mar 26, 2024
Merged

fix(postgres): empty socketDir by default #160

merged 3 commits into from
Mar 26, 2024

Conversation

shivaraj-bh
Copy link
Member

resolves #139

the solution is implemented based on #139 (comment)

An empty socketDir would mean that by default the postgres service will use TCP/IP instead of Unix-domain sockets.

> empty unix_socket_directories means not listening on any Unix-domain sockets, in which case only TCP/IP sockets can be used to connect to the server.

see: https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-UNIX-SOCKET-DIRECTORIES

* use TCP/IP by default for health check
@shivaraj-bh shivaraj-bh requested a review from srid March 26, 2024 12:47
Copy link
Member

@srid srid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shivaraj-bh
Copy link
Member Author

mentioned it as a warning

@shivaraj-bh shivaraj-bh merged commit 18d5c1d into main Mar 26, 2024
4 checks passed
@shivaraj-bh shivaraj-bh deleted the pg-socketdir branch March 26, 2024 13:14
shivaraj-bh added a commit that referenced this pull request Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

postgres: Document socket length limitation and workaround
2 participants