PostgreSQL remote access

postgresqlremote

I added remote host info on pg_hba.conf as:

host db1 all 10.6.169.88/27 trust

and also I did

listen_addresses = ‘*’
tcpip_socket = true

on postgresql.conf.

But still the remote client can not connect to db. What is the missing part about this? Remote client and host server is in different locations but with IT policies adjusted with correct ports and routes. So remote client is normally accessible to host server.

Here is what remote client gets as error:

Best Answer

It worked after editing the correct pg-hba.conf file. Well, earlier our customer asked us to move postgresql data to other drive partition. So there are two copies of conf files. One is inside postgresql program folder and the other is in data folder. To achieve what I want I needed to edit the one inside data folder.

Related Solutions

Postgresql – Automating failover in PostgreSQL 9.1

Check out repmrg:

repmgr is a set of open source tools that helps DBAs and System administrators manage a cluster of PostgreSQL databases..

By taking advantage of the Hot Standby capability introduced in PostgreSQL 9, repmgr greatly simplifies the process of setting up and managing database with high availability and scalability requirements.

repmgr simplifies administration and daily management, enhances productivity and reduces the overall costs of a PostgreSQL cluster by:

monitoring the replication process; allowing DBAs to issue high

availability operations such as switch-overs and fail-overs.

It does two things:

repmgr: command program that performs tasks on your cluster and then exits
repmgrd: management and monitoring daemon that watches the cluster and can automate remote actions.

For automatic failover, repmgrd does the trick and is not a SPOF in your network, like pgPool. However, it is still important to monitor all deamons and bring them back up after failure.

Version 2.0 is about to be released, including RPM's.

Sql-server – Cannot connect remotely to sql server 2012 instance using SSMS

You should not need to specify the port for a named instance (that's kind of the point of the name - and since it's dynamic you won't want to hard-code a port into your connection strings etc. unless you want to change your config files every time the port changes). Try connecting to:

123.123.123.123\SQLEXPRESS

Also make sure that your server is exposed to the Internet on that port (firewalls may be preventing this) and that the SQL Browser service is running.

PS Ping means nothing. You need to try to telnet to the port that SQL Server is exposed on.

Best Answer

Related Solutions

Postgresql – Automating failover in PostgreSQL 9.1

Sql-server – Cannot connect remotely to sql server 2012 instance using SSMS

Related Question