Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
| От | John R Pierce |
|---|---|
| Тема | Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL |
| Дата | |
| Msg-id | 4EFA19AB.7000905@hogranch.com обсуждение исходный текст |
| Ответ на | UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL (Jacques Lamothe <JLamothe@allconnect.com>) |
| Ответы |
Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
|
| Список | pgsql-general |
On 12/27/11 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. > is a linux firewall blocking incoming connections to 5436 ? iptables -L -vn to see the full set of firewall rules. -- john r pierce N 37, W 122 santa cruz ca mid-left coast
В списке pgsql-general по дате отправления: