Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
| От | Adrian Klaver |
|---|---|
| Тема | Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL |
| Дата | |
| Msg-id | 4EFA19B6.5020305@gmail.com обсуждение исходный текст |
| Ответ на | UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL (Jacques Lamothe <JLamothe@allconnect.com>) |
| Список | pgsql-general |
On 12/27/2011 11:07 AM, Jacques Lamothe wrote: > Hi, I have 2 cluster databases, running on the same host, Linux with > redHat. My fist database port is set to default, 5432, but my second > database port is set to 5436 in the postgresql.conf file. While > everything is ok with local connections, I cannot connect remotely using > any of my tools to the second database with port 5436, including > pgAdmin. Please help. Any parameter that I need to modify for the new > database with port 5436? I have attached the posgresql.conf. My guess is it is one of two things: 1) Did you restart the server after changing the value for listen_addresses? 2) Have you looked at the pg_hba.conf file to see if it allows remote connections? http://www.postgresql.org/docs/9.0/interactive/auth-pg-hba-conf.html > > Jay > > > > -- Adrian Klaver adrian.klaver@gmail.com
В списке pgsql-general по дате отправления: