On Fri, 2013-09-20 at 18:10 +0200, Michal Kozusznik wrote:
> A can confirm.
> A lot of unwanted behaviour in case of broken connection (including
> pgadmin crash).
> As far as I remember it has been reported multiple times, and answered
> that it is not possible to fix it due to ammount of work n
A can confirm.
A lot of unwanted behaviour in case of broken connection (including
pgadmin crash).
As far as I remember it has been reported multiple times, and answered
that it is not possible to fix it due to ammount of work needed.
I still cannot understand how is it possible in case of off
Apologies: I failed to mention that I am using Windows 7 x64 as my workstation
platform. The server is running on a unix variant.
And, yes, there are firewalls in between, that cut off sessions after x amount
of time.
Regards,
Peter
From: Belbin, Peter
Sent: Friday, September 20, 2013 10:09
Congrats on the good improvements to pgAdmin.
I do still find that when a connection to the distant postgresql server is
lost, that pgAdmin behaves badly and sometimes even has to be killed and
restarted.
What I see happening is akin to someone disconnecting the ethernet cable.
Eg: a firewall
Thanks a lot.
Pozdrawiam,
Bartek
2013/9/20 Dinesh Kumar
> Hi,
>
> Thanks for reporting this issue.
>
> Yes, this issue has been reported in the pgadmin generals, send some fixes
> as well. But unfortunately, the fix is not properly working on Mac machine
> where it's working on other platforms
Hi,
Thanks for reporting this issue.
Yes, this issue has been reported in the pgadmin generals, send some fixes
as well. But unfortunately, the fix is not properly working on Mac machine
where it's working on other platforms. I am trying to figure that out as
soon as possible and send a patch to
