Re: Unable to connect to Postgresql

From: rob stone <floriparob(at)gmail(dot)com>
To: John Iliffe <john(dot)iliffe(at)iliffe(dot)ca>, pgsql-general(at)postgresql(dot)org
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Joe Conway <mail(at)joeconway(dot)com>
Subject: Re: Unable to connect to Postgresql
Date: 2017-04-09 22:27:49
Message-ID: 1491776869.7940.4.camel@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello John,

Just saw this message.

>
> Still set to the default:
>
> #listen_addresses = 'localhost'         # what IP address(es) to
> listen on;
>                                         # comma-separated list of 
> addresses;
>                                         # defaults to 'localhost';
> use '*' 
> for all
>                                         # (change requires restart)
> #port = 5432                            # (change requires restart)
>
> I did change the Unix domain socket directories:
>
> #unix_socket_directories = '/tmp'       # comma-separated list of 
> directories
> unix_socket_directories = '/tmp,/var/pgsql'     # *****changed from
> default
> # 
>
>

Your set-up has Apache, PHP and Postgres all running from the same
machine.
So as far as running from there goes, it is "localhost".
There is no requirement to traverse a network. It is all on the same
physical machine.

Alter your postgresql.conf file and remove the hash so that:-

listen_addresses = 'localhost'

is explicitly defined. Alter pg_hba.conf so that localhost is declared
and let's see what happens.

Cheers,
Rob

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2017-04-10 00:01:32 Re: Unable to connect to Postgresql
Previous Message rob stone 2017-04-09 21:39:30 Re: Unable to connect to Postgresql