Re: Bug#411575: pgadmin3:

So,

Harri, thanks for these detailed instructions and thanks for your
feedback concerning 1.6.2, I bet pgadmin-hackers will appreciate
your positives comments ;).
Concerning this particular problem I found reference to such behaviours
in the mailing-lists archives.

Dave (project leader) included it to the todo list last november.

@Dave, anyone working on this particular topic:

/Attempt to reconnect to the server following a connection failure/

Regards,
Raph


Harri Kiiskinen a écrit :
> Hello Raphaël,
>
> I tried the 1.6.2 version, and the problem persists. Easy way to
> reproduce:
>
> - create a tunnel with ssh -L 15432:localhost:5432 to a server
> - define connection in pgadmin3 as locahost:15432
> - open database, execute a query in SQL window
> - close the ssh connection, and reopen it again
> - In the main pgadmin3 window, trying to access the connection, some
> error messages result (one would be enough, though), but the final
> window disconnects from the server and then it is easy to reconnect.
> - In the still open SQL window, the query cannot be executed, while the
> original connection was lost; the same connection can be opened only by
> first opening another connection and then re-opening the original one;
> even then, all other databases but the one originally used can be
> opened. The only way still seems to be to close the window and reopen it
> again.
>
> So the situation in this case has not improved in 1.6.2.
>
> Best Wishes,
> Harri
>
> PS. Otherwise 1.6.2 has quite nice improvements. The new structure of
> the main and SQL windows is much better. Probably much more to find out
> which I haven't found yet, also. Good work!
>
> ti, 2007-02-20 kello 09:56 +0100, Raphaël Enrici kirjoitti:
>