UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

From: Jacques Lamothe <JLamothe(at)allconnect(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Date: 2011-12-27 19:07:35
Message-ID: A464248CE14E60408AC030D3CD1790BA02708E@ACMAILNODE01.allconnect.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


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.

Jay

Attachment Content-Type Size
postgresql.conf application/octet-stream 16.8 KB

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2011-12-27 19:16:59 Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Previous Message Thomas Kellerer 2011-12-27 18:49:27 Re: Detecting uncommitted changes