Hi Andrew,
On Tue, Jul 3, 2018 at 10:06 AM, Andrew Pratt <andrewmpr...@gmail.com> wrote: > I really appreciate the huge effort that went into converting to a HTML > based UI for pgAdmin, we are working on similar projects for our products. > > I was just wondering whether you can review the handling of postgres > server connections within 4.3.1. > > Ideally, in my opinion, pgAdmin should always automatically re-establish a > lost connection. > There were a few issues related to this in 3.0 but they seem to have > gotten worse in 3.1 with items in the tree now not working if a connection > is lost and no re-connect dialog displays. > > I really fail to understand a good real world use case where anyone would > want the 'default' setting when they request something to happen to be > 'don't re-connect unless I tell you to' > > I also don't know why the connector to postgres that you are using takes > so long to recognise that the connection has dropped. > > We use Devart's Postgres connectors in our work and we perform a ping to > check a connection is still valid if it hasn't been used from the pool in a > while, which fails fast, allowing us to then re-connect the connection > quickly. Perhaps you could do something similar. At present it takes 10-30 > seconds to realise its disconnected, then a dialog sometimes appears to > reconnect and then you have to wait for it connect again which all seems > very slow compared to the metrics we achieve with devarts connectors. > > Please create an issue @ https://redmine.postgresql.org/projects/pgadmin4 > Thanks for considering!! > Andrew > Thanks, Khushboo
