Postgres Pro
Downloads
Home   >   mailing lists

UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL - Mailing list pgsql-general

From Jacques Lamothe
Subject UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Date
Msg-id A464248CE14E60408AC030D3CD1790BA02708E@ACMAILNODE01.allconnect.com
Whole thread Raw
Responses Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL  (John R Pierce <pierce@hogranch.com>)
Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL  (Adrian Klaver <adrian.klaver@gmail.com>)
Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL  (Raymond O'Donnell <rod@iol.ie>)
List pgsql-general
Tree view

 

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

pgsql-general by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: Detecting uncommitted changes
Next
From: John R Pierce
Date:
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL