Re: postgres port 5434 not being allowed when remote server isaccessing

No error - the connection attempt just spins until the attempt times out.

I now suspect a firewall issue and have reached out to our IT team to investigate.

Thank you,

On Wed, Aug 1, 2018 at 1:10 PM, Mariel Cherkassky <mariel.cherkassky@gmail.com> wrote:

Hi, what error do you get?

On Wed, Aug 1, 2018, 8:05 PM Mark Steben <mark.steben@drivedominion.com> wrote:

Hi Arlindo - yes hot_standby is turned on for that server.  Thanks for quick response.

On Wed, Aug 1, 2018 at 12:26 PM, Arlindo Neto <neto.acs@gmail.com> wrote:

Hello Mark,

Have you checked the hot_standby parameter? It must be ON so you can run queries on a standby.

Regards,

    Arlindo Neto.

Em qua, 1 de ago de 2018 às 13:22, Mark Steben <mark.steben@drivedominion.com> escreveu:

Good morning,

We run postgres 9.4.8 on our GNU linux standby server.  We run 3 instances receiving data there:

   1. a slony instance - port 5432

   2. standby instance 1 - port 5433

   3.  standby instance 2 - port 5434

We run connection strings in another GNU linux server to access the data on our standby server.

  We can access  the postgres instances on port 5432 and port 5433 but not port 5434.

All the instances are up and running on the standby server.  Any insights as to why 5434 does not work?