This particular version is a much better improvement than the one I first 
downloaded; I too had to increase the font size/windows size with ctrl-+ a few 
times.

 

TBH it’s still not fast but it’s now somewhat usable.

 

In short, a step in the right direction.

 

Thanks :)

 

DSL

 

From: Nigel Tucker [mailto:ni...@specialisedstructures.co.nz] 
Sent: Thursday, 6 July 2017 1:43 PM
To: 'Dave Page' <dp...@pgadmin.org>
Cc: pgadmin-supp...@postgresql.org
Subject: RE: Windows testing required: Updated runtime

 

Hi Dave,

 

I am finding similar load times to the others with your new version 1.5 – for 
me 12-14 seconds is much faster than before. What is really good is that 
everything else if working much faster – discovery of servers, connecting to 
specific server, acquisition of schemas, and tables.

 

Yes – I too get the ToString error mention elsewhere when showing data from the 
table, but works fine with an SQL Select.

 

The only other anomaly I have seen so far is that initially I started PgAdmin 
and it appeared very small along the top of the screen. I had to press Ctrl-+ a 
number of times to see anything. It has restarted just fine since then,

 

Thanks for the good work,

 

Nigel

 

Dr Nigel Tucker

System Architect

Specialised Structures NZ

Telephone Direct (NZ) +64 (0) 3 482 2473

 

                        

 

From: Dave Page [mailto:dp...@pgadmin.org] 
Sent: Friday, 7 July 2017 2:59 AM
To: pgadmin-hackers; pgAdmin Support
Subject: Windows testing required: Updated runtime

 

All,

 

I've put an interim build of pgAdmin 4 at 
https://developer.pgadmin.org/~dpage/pgadmin4-1.5-x86.exe for Windows users. 
This build uses a work in progress patch to replace the slow Qt components with 
ActiveQt + the Microsoft web browser control to significantly improve 
performance.

 

The version also includes close to 100 other bug fixes and changes, most 
noticeably performance improvements in the Query Tool that make it 
significantly faster than pgAdmin 3 with large result sets, and the ability to 
open the Query Tool and Debugger in new tabs that can be dragged onto different 
windows and therefore displays.

 

If you have the ability, please give it a test and let me know how it performs. 
There are some known issues that we're working on:

 

- The Query Tool History view isn't rendered correctly.

 

- Closing a tab is now detected when there's a dirty query tool window in it, 
but closing the window containing the tab is not.

 

- Inactive tabs have no visual definition between them. 

 

- When dragging a tab, the mouse icon changes to one with a stop sign in it.

 

- If you close the last tab in a child window, it doesn't close the window.

 

- Popout alerts don't display correctly.

 

Thanks!

 

-- 

Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Reply via email to