Обсуждение: BUG #13520: postgres not connecting with opnerp7.0

The following bug has been logged on the website:

Bug reference:      13520
Logged by:          MANOJ KUMAR
Email address:      manoj.itara@gmail.com
PostgreSQL version: 9.1.0
Operating system:   ubuntu 12.04
Description:

hai,
 I facing a issue while connecting postgres.Can you solve it.


Error:
psql: could not connect to server: No such file or directory
    Is the server running locally and accepting
    connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

"manoj.itara@gmail.com" <manoj.itara@gmail.com> wrote:

> I facing a issue while connecting postgres.Can you solve it.
>
> Error:
> psql: could not connect to server: No such file or directory
>     Is the server running locally and accepting
>     connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

This is not a bug; for future questions on usage, please send an
email to pgsql-general@postgresql.org, to post to the appropriate
list.

The hint says it all -- either the server is not running (and you
need to start it before you can connect), or it is running using a
different port number or subdirectory (and you should specify that
in your connection options).

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Kevin Grittner wrote:
> "manoj.itara@gmail.com" <manoj.itara@gmail.com> wrote:
>
> > I facing a issue while connecting postgres.Can you solve it.
> >
> > Error:
> > psql: could not connect to server: No such file or directory
> >     Is the server running locally and accepting
> >     connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
>
> This is not a bug; for future questions on usage, please send an
> email to pgsql-general@postgresql.org, to post to the appropriate
> list.
>
> The hint says it all -- either the server is not running (and you
> need to start it before you can connect), or it is running using a
> different port number or subdirectory (and you should specify that
> in your connection options).

Given the socket path in the HINT, I would suggest that the client
library has been installed via Debian packages, and the server probably
hasn't --- most likely, the socket is in the default path of /tmp.  So
if you try something like "host=/tmp" then it might be able to connect.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services