Package: dbconfig-pgsql Version: 2.0.4~bpo8+1 Severity: wishlist
Hi. As of now it seems, on cannot configure the socket dir and "port" that is used by dbconfig, when UNIX sockets are used with postgresql. Instead it seems it would always use /var/run/postgresql/.s.PGSQL.5432. But it's perfectly valid to have both, another dir and another "port" number and this is even supported out of the box by the debian postgresql packages, which allow to run multiple postgresql daemons per node, that then simply use different directories (for settings, DB data, etc.) and a different port (for TCP, and for the socket file name). See the pg_* tools from postgresql-common package, as well as the options: - port - unix_socket_directories in https://www.postgresql.org/docs/current/static/runtime-config-connection.html, the later which specifies the socket file pathname to be always: >In addition to the socket file itself, which is named .s.PGSQL.nnnn where >nnnn is the server's port number, an ordinary file named .s.PGSQL.nnnn.lock >will be created in each of the unix_socket_directories directories. Cheers, Chris. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
