Psql connect to unix socket

TCP sockets on localhost are usually implemented using UNIX domain sockets , so the answer on most systems is neglijable to none. In addition to the socket file itself, which is named. Neither file should ever be removed manually.

This parameter is irrelevant on Windows, which does not have Unix-domain sockets. All works from command line with psql. Unix -domain sockets use the usual Unix file system permission set. So the Pg side is correctly configured.

No such file or directory”. GIS extension), and when installe everything used to work fine. Also try using psql -h 127. It may be a configuration issue (disabled Unix sockets).

The configuration files and data should still be there, so simply doing apt-get install postgresql-9. The dpkg status of postgresql-9. To do this, you use the DriverManager. As you can see, it tries to use IPvconnection instead of the unix socket connection.

The you need to checkout postgresql. I suggested to see where it is putting the unix socket - either that or use lsof on the running postgres server process. There are sample pg_hba. Stack Exchange Network Stack Exchange network consists of 1QA communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

PostgreSQL is quite paranoid. But Grafana complains: 201. It incurs a small penalty over a local socket and therefore slightly higher latencies and is limited by the network bandwidth available.

Been trying to figure out the proper connection string to pass to DATABASE_URL. Previously Zabbix was connecting using a unix -style socket file (instead of a listening network socket ). Reconnecting in seconds. Try adding -h localhost to the psql command line. At the time of installing postgres to your operating system, it creates an initial DB and starts the postgres server domain running. U vivek -d sales Where,-h 192.

Specifies the host name of the machine or IP address (196.5) on which the server is running. It only takes a minute to. The connection failed because by default psql connects over UNIX sockets using peer authentication, that requires the current UNIX user to have the same user name as psql.

So you will have to create the UNIX user postgres and then login as postgres or use sudo -u postgres psql database-name for accessing the database (and psql should not ask for a password). Before you use the psql command you need to have access to a remote shell through SSH. Create a service account. Start the psql session.

I tried several configurations of database. Connections to unix sockets can also be made. This can be useful on distros like Ubuntu, where authentication is managed via the socket connection instead of a password.