From: | Durumdara <durumdara(at)gmail(dot)com> |
---|---|
To: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Conn. loose at some places | TCP keepalive |
Date: | 2018-02-13 13:47:20 |
Message-ID: | CAEcMXhkAHXOz9=Ed-3UPXnXggtjAWKaZR+J2j+5cJGyKdXZgpw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hello!
2018-02-13 12:48 GMT+01:00 Murtuza Zabuawala <
murtuza(dot)zabuawala(at)enterprisedb(dot)com>:
> I also use pgAdmin4 over vpn many times but I do not face any such issue,
> I think this is environment specific issue in your case.
>
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
>
With VPN I also haven't got problem. With SSL + cert + outer server I get
it in all inactive 5 minutes... :-(
My three colleauges too, but some other not.
Before I read the link I thought it's impossible to avoid, but PGAdmin III
successfully hacked with this technique...
I search for same option in PGAdmin IV, but I don't find now.
All libpq.dll based apps suffered this behaviour - pgsql, EMS SQL Manager,
Navicat, PGAdmin III/IV.
If I could define "onconnect" extra parameters or SQL commands somewhere, I
can change the TCP keepalive to lower, and the limitations would vanish...
Thanks
dd
From | Date | Subject | |
---|---|---|---|
Next Message | Murtuza Zabuawala | 2018-02-13 17:11:32 | Re: Conn. loose at some places | TCP keepalive |
Previous Message | Murtuza Zabuawala | 2018-02-13 11:48:53 | Re: Conn. loose at some places | TCP keepalive |