Thread: connection lost related issues are still *painful*
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 between my workstation and the server has a timeout, and is dropping the session.
It would be nice perhaps if there was a ‘noop’ kind of request that could be sent every so often as a keep-alive to ensure the connection does not get considered to be idle.
Regards,
Peter
This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.
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 AM
To: 'Dave Page'
Cc: PgAdmin Support
Subject: connection lost related issues are still *painful*
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 between my workstation and the server has a timeout, and is dropping the session.
It would be nice perhaps if there was a ‘noop’ kind of request that could be sent every so often as a keep-alive to ensure the connection does not get considered to be idle.
Regards,
Peter
This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.
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 official software packaged with postgresql :(
On 20.9.2013 17:10, Belbin, Peter wrote:
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 AM
To: 'Dave Page'
Cc: PgAdmin Support
Subject: connection lost related issues are still *painful*
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 between my workstation and the server has a timeout, and is dropping the session.
It would be nice perhaps if there was a ‘noop’ kind of request that could be sent every so often as a keep-alive to ensure the connection does not get considered to be idle.
Regards,
Peter
This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.
Attachment
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 needed. > > I still cannot understand how is it possible in case of official > software packaged with postgresql :( > Well, there are a limited number of hours in a day, and there are a limited number of developers of pgAdmin (Dave, sometimes some devs from EDB, and I on my free time... and actually, the devs from EDB pretty made 1.18, and I did nothing). So, back to the topic, yes, when something needs a huge amount of work to get fixed and is a hard subject, it tends not to be done. Nothing really surprising here. Once again, anybody who wants can help. Patches are welcome. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com