PGAdmin 3/4 do not handle Connection timeouts. (RM #3949)

[dpage]

Issue migrated from Redmine: https://redmine.postgresql.org/issues/3949
Originally created by Daniel J Oldenkamp at 2019-01-30 23:07:48 UTC.

How do you guys even use PG Admin with this fundamental ability broken?
Are you all closing out and re-opening PG Admin 10 times a day whenever you come back to the database?

If there was a button to reconnect this would solve most hardships.
Instead we have to wait for SQL connection timeout from application.

Ideally the software would check/re-establish a database connection at every command, but I would settle for a reconnect button.

Nothing is worth than having the application lock up and being unable to access a query you were in the middle of writing because heaven forbid you expanded a columns in the explorer and PG Admin had a heart attack.

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/3949#note-1
Originally created by Daniel J Oldenkamp at 2019-04-09 20:38:05 UTC.

There appears another bug associated with this issue.
with pgAdmin III sometimes when select the "refresh selected object" (the refresh button) after been inadvertently away for a few, the application crashes, force closing all open queries in an instant.

Most report writers have no access to their PostgreSQL configuration files.

Ideally the pgAdmin application could be configured to keep a session alive from the client side.

I know some people in the industry who will never to pgAdmin 4 and will help financially support the development of this feature into the pgAdmin 3 application.

[email protected]