You wrote this integrated with "pg_service.conf".
1.) I set server "service" to "BLAH".
cd "c:\Program Files (x86)\pgAdmin 4\v3\runtime"
"c:\Program Files (x86)\pgAdmin 4\v3\runtime\pgAdmin4.exe"
3.) I start PGA4 with this batch.
And then?
I want say that in PgAdmin III this "service" mode solved the timeouts, but the visual elements are changed, which caused more problems.
We have more multidatabase servers.
When I used PGA3 with service file, the service name used in every place when I saw database names formerly.
So I lost in navigation, because I must checked the opened database name to be sure that Query tool is in the DB what I needed.
I hope the PGA4 solution is better, it's not hide the database name (or replace with the service name).
Connection parameters are in server level, not in database.
