-
Notifications
You must be signed in to change notification settings - Fork 32
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
postgres: Document socket length limitation and workaround #139
Comments
We may want to have a separate page, |
Also, is $HOME the best place? Why not $TMPDIR (falling back to |
on darwin |
|
postgres doc mentioning the socket length limitation: #147 |
This might not be as straight forward as it seems. Let’s assume that the |
What happens if we don't set this option in the first place? What is postgres' default -- and is that sufficient? services-flake/nix/postgres/default.nix Line 201 in 18f9dec
|
It will use |
https://www.postgresql.org/docs/current/runtime-config-connection.html So, the nixpkgs package uses something else as default? Also, it looks like we can disable this entirely:
(Will that break anything in CI though?) |
I was looking to disable, let me try it out. |
https://devenv.sh/blog/2023/03/20/devenv-10-rewrite-in-rust/#devenv_runtime |
resolves #139 > 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
#77
The text was updated successfully, but these errors were encountered: