Обсуждение: Windows testing required: Updated runtime
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day
www.folkalley.com
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day
www.folkalley.com
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Dave,The good and the ugly.The good.I restarted Windows and it now starts in 15 secs, down from 20 secs.
The ugly.The version is not usable. The screen/menu is incomprehensible.
System Details:Windows 10 HomeProcessor: Intel Pentium CPU G3220 3.0GhzGPU: AMD Radeon HD 6450Memory: 8.00 GB *(3.47 GB usable)32-bit O/SDual monitorsMelvin Davidson 🎸
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day
www.folkalley.comOn Thursday, July 6, 2017, 10:59:42 AM EDT, Dave Page <dpage@pgadmin.org> wrote: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
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Dave,The good and the ugly.The good.I restarted Windows and it now starts in 15 secs, down from 20 secs.
The ugly.The version is not usable. The screen/menu is incomprehensible.
System Details:Windows 10 HomeProcessor: Intel Pentium CPU G3220 3.0GhzGPU: AMD Radeon HD 6450Memory: 8.00 GB *(3.47 GB usable)32-bit O/SDual monitorsMelvin Davidson 🎸
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day
www.folkalley.comOn Thursday, July 6, 2017, 10:59:42 AM EDT, Dave Page <dpage@pgadmin.org> wrote: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
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Much improved load time - 14 seconds - Windows 10 x64.
When I tried to query all the rows in a table using the context menu, the new tab is added and can be moved to a different window, but the following error was generated and the window was blank.
Cheers,
George
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
-- Cleartag Software, Inc. 972 McMillan Avenue Winnipeg, MB R3M 0V7 (204) 284-9839 phone/cell (204) 284-9838 fax gweaver@cleartagsoftware.com Fast. Accurate. Easy.
Much improved load time - 14 seconds - Windows 10 x64.
When I tried to query all the rows in a table using the context menu, the new tab is added and can be moved to a different window, but the following error was generated and the window was blank.
Cheers,
George
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
-- Cleartag Software, Inc. 972 McMillan Avenue Winnipeg, MB R3M 0V7 (204) 284-9839 phone/cell (204) 284-9838 fax gweaver@cleartagsoftware.com Fast. Accurate. Easy.
Hi Dave,
Much improved load time - 14 seconds - Windows 10 x64.
When I tried to query all the rows in a table using the context menu, the new tab is added and can be moved to a different window, but the following error was generated and the window was blank.
Cheers,
GeorgeOn 06/07/2017 9:59 AM, Dave Page wrote: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-- Cleartag Software, Inc. 972 McMillan Avenue Winnipeg, MB R3M 0V7 (204) 284-9839 phone/cell (204) 284-9838 fax gweaver@cleartagsoftware.com Fast. Accurate. Easy.
Hi Dave,
Much improved load time - 14 seconds - Windows 10 x64.
When I tried to query all the rows in a table using the context menu, the new tab is added and can be moved to a different window, but the following error was generated and the window was blank.
Cheers,
GeorgeOn 06/07/2017 9:59 AM, Dave Page wrote: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-- Cleartag Software, Inc. 972 McMillan Avenue Winnipeg, MB R3M 0V7 (204) 284-9839 phone/cell (204) 284-9838 fax gweaver@cleartagsoftware.com Fast. Accurate. Easy.
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
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
I also tested Windows installers and script error displayed and here is the RM ID:
------
https://redmine.postgresql.org/issues/2542
On Thu, Jul 6, 2017 at 7:59 AM, Dave Page <dpage@pgadmin.org> wrote: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 CompanyHi Dave,At first, I was not having the same positive experience as the others. After installation, the "Loading pgAdmin 4 v1.5..." message with the spinning icon just appeared indefinitely. After several minutes, I canceled it. Then I tried it again, and got this message:Error loading script - /sqleditor/sqleditorError messageundefinedThen I disabled my AV software, and all was well. It launched in about 11 seconds (down from the 33 seconds I was getting on the previous version.)I'll test it out a little further later.Thank you,Shira
--
Phone Direct: +92-51-8466803
Mobile: +92-333-5409707
Skype ID: syed.fahar.abbas
Website: www.enterprisedb.com
I also tested Windows installers and script error displayed and here is the RM ID:
------
https://redmine.postgresql.org/issues/2542
On Thu, Jul 6, 2017 at 7:59 AM, Dave Page <dpage@pgadmin.org> wrote: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 CompanyHi Dave,At first, I was not having the same positive experience as the others. After installation, the "Loading pgAdmin 4 v1.5..." message with the spinning icon just appeared indefinitely. After several minutes, I canceled it. Then I tried it again, and got this message:Error loading script - /sqleditor/sqleditorError messageundefinedThen I disabled my AV software, and all was well. It launched in about 11 seconds (down from the 33 seconds I was getting on the previous version.)I'll test it out a little further later.Thank you,Shira
--
Phone Direct: +92-51-8466803
Mobile: +92-333-5409707
Skype ID: syed.fahar.abbas
Website: www.enterprisedb.com
Hi Dave
30 second start-up so still very slow for me.
Consistently get an exception when closing( see attachment)
Did webpack not make it?
I still get 167 requests on start up.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
Вложения
Hi Dave
30 second start-up so still very slow for me.
Consistently get an exception when closing( see attachment)
Did webpack not make it?
I still get 167 requests on start up.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
Вложения
Hi Dave
30 second start-up so still very slow for me.
Consistently get an exception when closing( see attachment)
Did webpack not make it?
I still get 167 requests on start up.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave
30 second start-up so still very slow for me.
Consistently get an exception when closing( see attachment)
Did webpack not make it?
I still get 167 requests on start up.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
HI Dave
Machine is
Windows 7 x64
Intel Core 6400 2.33GHz 6GB ram
SSD
I can no longer start pgAdmin the progress wheel just keeps running. and it never gets to dashboard.
Not much info sorry.
The Event log for exception on close is
Log Name: Application
Source: Application Error
Date: 07/07/2017 10:05:51
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: aes15win7.surcouf.local
Description:
Faulting application name: pgAdmin4.exe, version: 1.5.0.0, time stamp: 0x595e3603
Faulting module name: Qt5Core.dll, version: 5.8.0.0, time stamp: 0x587fd30b
Exception code: 0xc0000005
Fault offset: 0x0016ced8
Faulting process id: 0x1b28
Faulting application start time: 0x01d2f6fffeab9d36
Faulting application path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
Faulting module path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll
Report Id: 78f82194-62f3-11e7-a69f-0019b91a41aa
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-07-07T09:05:51.000000000Z" />
<EventRecordID>99764</EventRecordID>
<Channel>Application</Channel>
<Computer>aes15win7.surcouf.local</Computer>
<Security />
</System>
<EventData>
<Data>pgAdmin4.exe</Data>
<Data>1.5.0.0</Data>
<Data>595e3603</Data>
<Data>Qt5Core.dll</Data>
<Data>5.8.0.0</Data>
<Data>587fd30b</Data>
<Data>c0000005</Data>
<Data>0016ced8</Data>
<Data>1b28</Data>
<Data>01d2f6fffeab9d36</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll</Data>
<Data>78f82194-62f3-11e7-a69f-0019b91a41aa</Data>
</EventData>
</Event>
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 09:39
To: Mike Surcouf
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Fri, Jul 7, 2017 at 9:20 AM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
30 second start-up so still very slow for me.
That's strange - I get < 12s even on my underpowered virtual machine.
What spec machine are you running? Can you try with AV disabled?
Consistently get an exception when closing( see attachment)
Also strange. I do not see that. Is there any more info in the event log etc?
Did webpack not make it?
I still get 167 requests on start up.
The basic infrastructure is there now, and we've made almost all the JS code static now so it avoids the templating engine, but there's still work to do to pack it all.
Thanks.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
HI Dave
Machine is
Windows 7 x64
Intel Core 6400 2.33GHz 6GB ram
SSD
I can no longer start pgAdmin the progress wheel just keeps running. and it never gets to dashboard.
Not much info sorry.
The Event log for exception on close is
Log Name: Application
Source: Application Error
Date: 07/07/2017 10:05:51
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: aes15win7.surcouf.local
Description:
Faulting application name: pgAdmin4.exe, version: 1.5.0.0, time stamp: 0x595e3603
Faulting module name: Qt5Core.dll, version: 5.8.0.0, time stamp: 0x587fd30b
Exception code: 0xc0000005
Fault offset: 0x0016ced8
Faulting process id: 0x1b28
Faulting application start time: 0x01d2f6fffeab9d36
Faulting application path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
Faulting module path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll
Report Id: 78f82194-62f3-11e7-a69f-0019b91a41aa
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-07-07T09:05:51.000000000Z" />
<EventRecordID>99764</EventRecordID>
<Channel>Application</Channel>
<Computer>aes15win7.surcouf.local</Computer>
<Security />
</System>
<EventData>
<Data>pgAdmin4.exe</Data>
<Data>1.5.0.0</Data>
<Data>595e3603</Data>
<Data>Qt5Core.dll</Data>
<Data>5.8.0.0</Data>
<Data>587fd30b</Data>
<Data>c0000005</Data>
<Data>0016ced8</Data>
<Data>1b28</Data>
<Data>01d2f6fffeab9d36</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll</Data>
<Data>78f82194-62f3-11e7-a69f-0019b91a41aa</Data>
</EventData>
</Event>
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 09:39
To: Mike Surcouf
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Fri, Jul 7, 2017 at 9:20 AM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
30 second start-up so still very slow for me.
That's strange - I get < 12s even on my underpowered virtual machine.
What spec machine are you running? Can you try with AV disabled?
Consistently get an exception when closing( see attachment)
Also strange. I do not see that. Is there any more info in the event log etc?
Did webpack not make it?
I still get 167 requests on start up.
The basic infrastructure is there now, and we've made almost all the JS code static now so it avoids the templating engine, but there's still work to do to pack it all.
Thanks.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
IN addition I uninstalled removed everything in %APPDATA%\pgadmin4 and programfiles and restarted reinstalled.
Also trying with AV disabled.
Unfortunately I still get the same results.
From: Mike Surcouf [mailto:mikes@surcouf.co.uk]
Sent: 07 July 2017 10:17
To: 'Dave Page'
Cc: pgadmin-hackers; pgAdmin Support
Subject: RE: Windows testing required: Updated runtime
HI Dave
Machine is
Windows 7 x64
Intel Core 6400 2.33GHz 6GB ram
SSD
I can no longer start pgAdmin the progress wheel just keeps running. and it never gets to dashboard.
Not much info sorry.
The Event log for exception on close is
Log Name: Application
Source: Application Error
Date: 07/07/2017 10:05:51
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: aes15win7.surcouf.local
Description:
Faulting application name: pgAdmin4.exe, version: 1.5.0.0, time stamp: 0x595e3603
Faulting module name: Qt5Core.dll, version: 5.8.0.0, time stamp: 0x587fd30b
Exception code: 0xc0000005
Fault offset: 0x0016ced8
Faulting process id: 0x1b28
Faulting application start time: 0x01d2f6fffeab9d36
Faulting application path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
Faulting module path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll
Report Id: 78f82194-62f3-11e7-a69f-0019b91a41aa
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-07-07T09:05:51.000000000Z" />
<EventRecordID>99764</EventRecordID>
<Channel>Application</Channel>
<Computer>aes15win7.surcouf.local</Computer>
<Security />
</System>
<EventData>
<Data>pgAdmin4.exe</Data>
<Data>1.5.0.0</Data>
<Data>595e3603</Data>
<Data>Qt5Core.dll</Data>
<Data>5.8.0.0</Data>
<Data>587fd30b</Data>
<Data>c0000005</Data>
<Data>0016ced8</Data>
<Data>1b28</Data>
<Data>01d2f6fffeab9d36</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll</Data>
<Data>78f82194-62f3-11e7-a69f-0019b91a41aa</Data>
</EventData>
</Event>
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 09:39
To: Mike Surcouf
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Fri, Jul 7, 2017 at 9:20 AM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
30 second start-up so still very slow for me.
That's strange - I get < 12s even on my underpowered virtual machine.
What spec machine are you running? Can you try with AV disabled?
Consistently get an exception when closing( see attachment)
Also strange. I do not see that. Is there any more info in the event log etc?
Did webpack not make it?
I still get 167 requests on start up.
The basic infrastructure is there now, and we've made almost all the JS code static now so it avoids the templating engine, but there's still work to do to pack it all.
Thanks.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
IN addition I uninstalled removed everything in %APPDATA%\pgadmin4 and programfiles and restarted reinstalled.
Also trying with AV disabled.
Unfortunately I still get the same results.
From: Mike Surcouf [mailto:mikes@surcouf.co.uk]
Sent: 07 July 2017 10:17
To: 'Dave Page'
Cc: pgadmin-hackers; pgAdmin Support
Subject: RE: Windows testing required: Updated runtime
HI Dave
Machine is
Windows 7 x64
Intel Core 6400 2.33GHz 6GB ram
SSD
I can no longer start pgAdmin the progress wheel just keeps running. and it never gets to dashboard.
Not much info sorry.
The Event log for exception on close is
Log Name: Application
Source: Application Error
Date: 07/07/2017 10:05:51
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: aes15win7.surcouf.local
Description:
Faulting application name: pgAdmin4.exe, version: 1.5.0.0, time stamp: 0x595e3603
Faulting module name: Qt5Core.dll, version: 5.8.0.0, time stamp: 0x587fd30b
Exception code: 0xc0000005
Fault offset: 0x0016ced8
Faulting process id: 0x1b28
Faulting application start time: 0x01d2f6fffeab9d36
Faulting application path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
Faulting module path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll
Report Id: 78f82194-62f3-11e7-a69f-0019b91a41aa
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-07-07T09:05:51.000000000Z" />
<EventRecordID>99764</EventRecordID>
<Channel>Application</Channel>
<Computer>aes15win7.surcouf.local</Computer>
<Security />
</System>
<EventData>
<Data>pgAdmin4.exe</Data>
<Data>1.5.0.0</Data>
<Data>595e3603</Data>
<Data>Qt5Core.dll</Data>
<Data>5.8.0.0</Data>
<Data>587fd30b</Data>
<Data>c0000005</Data>
<Data>0016ced8</Data>
<Data>1b28</Data>
<Data>01d2f6fffeab9d36</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll</Data>
<Data>78f82194-62f3-11e7-a69f-0019b91a41aa</Data>
</EventData>
</Event>
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 09:39
To: Mike Surcouf
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Fri, Jul 7, 2017 at 9:20 AM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
30 second start-up so still very slow for me.
That's strange - I get < 12s even on my underpowered virtual machine.
What spec machine are you running? Can you try with AV disabled?
Consistently get an exception when closing( see attachment)
Also strange. I do not see that. Is there any more info in the event log etc?
Did webpack not make it?
I still get 167 requests on start up.
The basic infrastructure is there now, and we've made almost all the JS code static now so it avoids the templating engine, but there's still work to do to pack it all.
Thanks.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
IN addition I uninstalled removed everything in %APPDATA%\pgadmin4 and programfiles and restarted reinstalled.
Also trying with AV disabled.
Unfortunately I still get the same results.
From: Mike Surcouf [mailto:mikes@surcouf.co.uk]
Sent: 07 July 2017 10:17
To: 'Dave Page'
Cc: pgadmin-hackers; pgAdmin Support
Subject: RE: Windows testing required: Updated runtime
HI Dave
Machine is
Windows 7 x64
Intel Core 6400 2.33GHz 6GB ram
SSD
I can no longer start pgAdmin the progress wheel just keeps running. and it never gets to dashboard.
Not much info sorry.
The Event log for exception on close is
Log Name: Application
Source: Application Error
Date: 07/07/2017 10:05:51
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: aes15win7.surcouf.local
Description:
Faulting application name: pgAdmin4.exe, version: 1.5.0.0, time stamp: 0x595e3603
Faulting module name: Qt5Core.dll, version: 5.8.0.0, time stamp: 0x587fd30b
Exception code: 0xc0000005
Fault offset: 0x0016ced8
Faulting process id: 0x1b28
Faulting application start time: 0x01d2f6fffeab9d36
Faulting application path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
Faulting module path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll
Report Id: 78f82194-62f3-11e7-a69f-
0019b91a41aa Event Xml:
<Event xmlns="http://schemas.
microsoft.com/win/2004/08/ events/event"> <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</
Keywords> <TimeCreated SystemTime="2017-07-07T09:05:
51.000000000Z" /> <EventRecordID>99764</
EventRecordID> <Channel>Application</Channel>
<Computer>aes15win7.surcouf.
local</Computer> <Security />
</System>
<EventData>
<Data>pgAdmin4.exe</Data>
<Data>1.5.0.0</Data>
<Data>595e3603</Data>
<Data>Qt5Core.dll</Data>
<Data>5.8.0.0</Data>
<Data>587fd30b</Data>
<Data>c0000005</Data>
<Data>0016ced8</Data>
<Data>1b28</Data>
<Data>01d2f6fffeab9d36</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe</
Data> <Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll</
Data> <Data>78f82194-62f3-11e7-a69f-
0019b91a41aa</Data> </EventData>
</Event>
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 09:39
To: Mike Surcouf
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Fri, Jul 7, 2017 at 9:20 AM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
30 second start-up so still very slow for me.
That's strange - I get < 12s even on my underpowered virtual machine.
What spec machine are you running? Can you try with AV disabled?
Consistently get an exception when closing( see attachment)
Also strange. I do not see that. Is there any more info in the event log etc?
Did webpack not make it?
I still get 167 requests on start up.
The basic infrastructure is there now, and we've made almost all the JS code static now so it avoids the templating engine, but there's still work to do to pack it all.
Thanks.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
IN addition I uninstalled removed everything in %APPDATA%\pgadmin4 and programfiles and restarted reinstalled.
Also trying with AV disabled.
Unfortunately I still get the same results.
From: Mike Surcouf [mailto:mikes@surcouf.co.uk]
Sent: 07 July 2017 10:17
To: 'Dave Page'
Cc: pgadmin-hackers; pgAdmin Support
Subject: RE: Windows testing required: Updated runtime
HI Dave
Machine is
Windows 7 x64
Intel Core 6400 2.33GHz 6GB ram
SSD
I can no longer start pgAdmin the progress wheel just keeps running. and it never gets to dashboard.
Not much info sorry.
The Event log for exception on close is
Log Name: Application
Source: Application Error
Date: 07/07/2017 10:05:51
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: aes15win7.surcouf.local
Description:
Faulting application name: pgAdmin4.exe, version: 1.5.0.0, time stamp: 0x595e3603
Faulting module name: Qt5Core.dll, version: 5.8.0.0, time stamp: 0x587fd30b
Exception code: 0xc0000005
Fault offset: 0x0016ced8
Faulting process id: 0x1b28
Faulting application start time: 0x01d2f6fffeab9d36
Faulting application path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
Faulting module path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll
Report Id: 78f82194-62f3-11e7-a69f-
0019b91a41aa Event Xml:
<Event xmlns="http://schemas.
microsoft.com/win/2004/08/ events/event"> <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</
Keywords> <TimeCreated SystemTime="2017-07-07T09:05:
51.000000000Z" /> <EventRecordID>99764</
EventRecordID> <Channel>Application</Channel>
<Computer>aes15win7.surcouf.
local</Computer> <Security />
</System>
<EventData>
<Data>pgAdmin4.exe</Data>
<Data>1.5.0.0</Data>
<Data>595e3603</Data>
<Data>Qt5Core.dll</Data>
<Data>5.8.0.0</Data>
<Data>587fd30b</Data>
<Data>c0000005</Data>
<Data>0016ced8</Data>
<Data>1b28</Data>
<Data>01d2f6fffeab9d36</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe</
Data> <Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll</
Data> <Data>78f82194-62f3-11e7-a69f-
0019b91a41aa</Data> </EventData>
</Event>
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 09:39
To: Mike Surcouf
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Fri, Jul 7, 2017 at 9:20 AM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
30 second start-up so still very slow for me.
That's strange - I get < 12s even on my underpowered virtual machine.
What spec machine are you running? Can you try with AV disabled?
Consistently get an exception when closing( see attachment)
Also strange. I do not see that. Is there any more info in the event log etc?
Did webpack not make it?
I still get 167 requests on start up.
The basic infrastructure is there now, and we've made almost all the JS code static now so it avoids the templating engine, but there's still work to do to pack it all.
Thanks.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave that was a type yes I deleted pgAdmin under appdata
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 12:40
To: Mike Surcouf
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
If you've done that, then you really have removed everything except for a handful of registry entries. To completely start over you should:
- Uninstall pgAdmin
- Ensure the original installation directory is removed entirely.
- Remove "%APPDATA%\pgAdmin" (not %APPDATA%\pgAdmin4)
- Remove "HKEY_CURRENT_USER\Software\pgadmin" from the registry
- Restart (probably not required, but...)
- Reinstall pgAdmin.
On Fri, Jul 7, 2017 at 10:29 AM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
IN addition I uninstalled removed everything in %APPDATA%\pgadmin4 and programfiles and restarted reinstalled.
Also trying with AV disabled.
Unfortunately I still get the same results.
From: Mike Surcouf [mailto:mikes@surcouf.co.uk]
Sent: 07 July 2017 10:17
To: 'Dave Page'
Cc: pgadmin-hackers; pgAdmin Support
Subject: RE: Windows testing required: Updated runtime
HI Dave
Machine is
Windows 7 x64
Intel Core 6400 2.33GHz 6GB ram
SSD
I can no longer start pgAdmin the progress wheel just keeps running. and it never gets to dashboard.
Not much info sorry.
The Event log for exception on close is
Log Name: Application
Source: Application Error
Date: 07/07/2017 10:05:51
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: aes15win7.surcouf.local
Description:
Faulting application name: pgAdmin4.exe, version: 1.5.0.0, time stamp: 0x595e3603
Faulting module name: Qt5Core.dll, version: 5.8.0.0, time stamp: 0x587fd30b
Exception code: 0xc0000005
Fault offset: 0x0016ced8
Faulting process id: 0x1b28
Faulting application start time: 0x01d2f6fffeab9d36
Faulting application path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
Faulting module path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll
Report Id: 78f82194-62f3-11e7-a69f-0019b91a41aa
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-07-07T09:05:51.000000000Z" />
<EventRecordID>99764</EventRecordID>
<Channel>Application</Channel>
<Computer>aes15win7.surcouf.local</Computer>
<Security />
</System>
<EventData>
<Data>pgAdmin4.exe</Data>
<Data>1.5.0.0</Data>
<Data>595e3603</Data>
<Data>Qt5Core.dll</Data>
<Data>5.8.0.0</Data>
<Data>587fd30b</Data>
<Data>c0000005</Data>
<Data>0016ced8</Data>
<Data>1b28</Data>
<Data>01d2f6fffeab9d36</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll</Data>
<Data>78f82194-62f3-11e7-a69f-0019b91a41aa</Data>
</EventData>
</Event>
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 09:39
To: Mike Surcouf
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Fri, Jul 7, 2017 at 9:20 AM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
30 second start-up so still very slow for me.
That's strange - I get < 12s even on my underpowered virtual machine.
What spec machine are you running? Can you try with AV disabled?
Consistently get an exception when closing( see attachment)
Also strange. I do not see that. Is there any more info in the event log etc?
Did webpack not make it?
I still get 167 requests on start up.
The basic infrastructure is there now, and we've made almost all the JS code static now so it avoids the templating engine, but there's still work to do to pack it all.
Thanks.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave that was a type yes I deleted pgAdmin under appdata
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 12:40
To: Mike Surcouf
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
If you've done that, then you really have removed everything except for a handful of registry entries. To completely start over you should:
- Uninstall pgAdmin
- Ensure the original installation directory is removed entirely.
- Remove "%APPDATA%\pgAdmin" (not %APPDATA%\pgAdmin4)
- Remove "HKEY_CURRENT_USER\Software\pgadmin" from the registry
- Restart (probably not required, but...)
- Reinstall pgAdmin.
On Fri, Jul 7, 2017 at 10:29 AM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
IN addition I uninstalled removed everything in %APPDATA%\pgadmin4 and programfiles and restarted reinstalled.
Also trying with AV disabled.
Unfortunately I still get the same results.
From: Mike Surcouf [mailto:mikes@surcouf.co.uk]
Sent: 07 July 2017 10:17
To: 'Dave Page'
Cc: pgadmin-hackers; pgAdmin Support
Subject: RE: Windows testing required: Updated runtime
HI Dave
Machine is
Windows 7 x64
Intel Core 6400 2.33GHz 6GB ram
SSD
I can no longer start pgAdmin the progress wheel just keeps running. and it never gets to dashboard.
Not much info sorry.
The Event log for exception on close is
Log Name: Application
Source: Application Error
Date: 07/07/2017 10:05:51
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: aes15win7.surcouf.local
Description:
Faulting application name: pgAdmin4.exe, version: 1.5.0.0, time stamp: 0x595e3603
Faulting module name: Qt5Core.dll, version: 5.8.0.0, time stamp: 0x587fd30b
Exception code: 0xc0000005
Fault offset: 0x0016ced8
Faulting process id: 0x1b28
Faulting application start time: 0x01d2f6fffeab9d36
Faulting application path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
Faulting module path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll
Report Id: 78f82194-62f3-11e7-a69f-0019b91a41aa
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-07-07T09:05:51.000000000Z" />
<EventRecordID>99764</EventRecordID>
<Channel>Application</Channel>
<Computer>aes15win7.surcouf.local</Computer>
<Security />
</System>
<EventData>
<Data>pgAdmin4.exe</Data>
<Data>1.5.0.0</Data>
<Data>595e3603</Data>
<Data>Qt5Core.dll</Data>
<Data>5.8.0.0</Data>
<Data>587fd30b</Data>
<Data>c0000005</Data>
<Data>0016ced8</Data>
<Data>1b28</Data>
<Data>01d2f6fffeab9d36</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe</Data>
<Data>C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5Core.dll</Data>
<Data>78f82194-62f3-11e7-a69f-0019b91a41aa</Data>
</EventData>
</Event>
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 09:39
To: Mike Surcouf
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Fri, Jul 7, 2017 at 9:20 AM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
30 second start-up so still very slow for me.
That's strange - I get < 12s even on my underpowered virtual machine.
What spec machine are you running? Can you try with AV disabled?
Consistently get an exception when closing( see attachment)
Also strange. I do not see that. Is there any more info in the event log etc?
Did webpack not make it?
I still get 167 requests on start up.
The basic infrastructure is there now, and we've made almost all the JS code static now so it avoids the templating engine, but there's still work to do to pack it all.
Thanks.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 06 July 2017 15:59
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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
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.
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.
On Thu, Jul 6, 2017 at 7:59 AM, Dave Page <dpage@pgadmin.org> wrote: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.It starts quite a bit faster than it used to. It used to be close to a minute, now it is 15 seconds from cold and 10 if it were recently running and then started again.I haven't really played with the features, so don't have anything to report there.Cheers,Jeff
On Thu, Jul 6, 2017 at 7:59 AM, Dave Page <dpage@pgadmin.org> wrote: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.It starts quite a bit faster than it used to. It used to be close to a minute, now it is 15 seconds from cold and 10 if it were recently running and then started again.I haven't really played with the features, so don't have anything to report there.Cheers,Jeff
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall.
Ross
Ross McDonald | GIS Data Coordinator | Angus Council, People, IT | Angus House, Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT | t: 01307 476419
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 09:46
To: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
All,
Thank you to those that have tested this build. With a couple of exceptions, most folks seem to be reporting the improved performance we hoped for. There is more work to do to finish up this patch which is underway, and there is also additional optimisation work being done for future releases.
I am interested to know if anyone has tried either with a proxy server or over a remote desktop session. We've fixed issues in both of those areas before, and it would be good to get confirmation that we haven't broken anything again.
Melvin has noted that once upgraded to this test release, you cannot go back to the "real" 1.5 (as it won't run). I believe that is due to changes in the configuration database. The easy fix is to move %APPDATA%\pgAdmin\pgadmin4.db out of the way and then start pgAdmin. Unfortunately this will mean servers will need to be re-added, and config options will have reset to default. It is possible to revert the changes to the DB, but that's somewhat fiddly. If anyone really needs to do that, let me know and I'll write up instructions. Apologies if that causes anyone problems.
Thanks!
On Thu, Jul 6, 2017 at 3:59 PM, Dave Page <dpage@pgadmin.org> wrote:
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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
This message is strictly confidential. If you have received this in error, please inform the sender and remove it from your system. If received in error you may not copy, print, forward or use it or any attachment in any way. This message is not capable of creating a legal contract or a binding representation and does not represent the views of Angus Council. Emails may be monitored for security and network management reasons. Messages containing inappropriate content may be intercepted. Angus Council does not accept any liability for any harm that may be caused to the recipient system or data on it by this message or any attachment.
Вложения
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall.
Ross
Ross McDonald | GIS Data Coordinator | Angus Council, People, IT | Angus House, Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT | t: 01307 476419
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 07 July 2017 09:46
To: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
All,
Thank you to those that have tested this build. With a couple of exceptions, most folks seem to be reporting the improved performance we hoped for. There is more work to do to finish up this patch which is underway, and there is also additional optimisation work being done for future releases.
I am interested to know if anyone has tried either with a proxy server or over a remote desktop session. We've fixed issues in both of those areas before, and it would be good to get confirmation that we haven't broken anything again.
Melvin has noted that once upgraded to this test release, you cannot go back to the "real" 1.5 (as it won't run). I believe that is due to changes in the configuration database. The easy fix is to move %APPDATA%\pgAdmin\pgadmin4.db out of the way and then start pgAdmin. Unfortunately this will mean servers will need to be re-added, and config options will have reset to default. It is possible to revert the changes to the DB, but that's somewhat fiddly. If anyone really needs to do that, let me know and I'll write up instructions. Apologies if that causes anyone problems.
Thanks!
On Thu, Jul 6, 2017 at 3:59 PM, Dave Page <dpage@pgadmin.org> wrote:
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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
This message is strictly confidential. If you have received this in error, please inform the sender and remove it from your system. If received in error you may not copy, print, forward or use it or any attachment in any way. This message is not capable of creating a legal contract or a binding representation and does not represent the views of Angus Council. Emails may be monitored for security and network management reasons. Messages containing inappropriate content may be intercepted. Angus Council does not accept any liability for any harm that may be caused to the recipient system or data on it by this message or any attachment.
Вложения
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\
Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\
pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\
Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\
pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave
Can I suggest you send out another build before you go GA.
I for one have outstanding issues that were not in 1.3 (see previous emails).
I know you said you don’t have my issues on your install but that doesn’t mean they don’t exist.
Happy to test
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:11
To: McDonaldR
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <McDonaldR@angus.gov.uk> wrote:
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Thanks - this should be fixed for GA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave
Can I suggest you send out another build before you go GA.
I for one have outstanding issues that were not in 1.3 (see previous emails).
I know you said you don’t have my issues on your install but that doesn’t mean they don’t exist.
Happy to test
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:11
To: McDonaldR
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <McDonaldR@angus.gov.uk> wrote:
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Thanks - this should be fixed for GA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave
Can I suggest you send out another build before you go GA.
I for one have outstanding issues that were not in 1.3 (see previous emails).
I know you said you don’t have my issues on your install but that doesn’t mean they don’t exist.
Happy to test
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:11
To: McDonaldR
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <McDonaldR@angus.gov.uk> wrote:
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\
Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\
pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Thanks - this should be fixed for GA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave
Can I suggest you send out another build before you go GA.
I for one have outstanding issues that were not in 1.3 (see previous emails).
I know you said you don’t have my issues on your install but that doesn’t mean they don’t exist.
Happy to test
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:11
To: McDonaldR
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <McDonaldR@angus.gov.uk> wrote:
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\
Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\
pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Thanks - this should be fixed for GA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:52
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
The candidate build can be found at https://developer.pgadmin.org/~dpage/1.6/.
Note that as the timing is coupled with the PostgreSQL 10b2 release, we'll only rewrap now for showstopper issues, not anything minor.
On Tue, Jul 11, 2017 at 1:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
Can I suggest you send out another build before you go GA.
I for one have outstanding issues that were not in 1.3 (see previous emails).
I know you said you don’t have my issues on your install but that doesn’t mean they don’t exist.
Happy to test
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:11
To: McDonaldR
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <McDonaldR@angus.gov.uk> wrote:
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Thanks - this should be fixed for GA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:52
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
The candidate build can be found at https://developer.pgadmin.org/~dpage/1.6/.
Note that as the timing is coupled with the PostgreSQL 10b2 release, we'll only rewrap now for showstopper issues, not anything minor.
On Tue, Jul 11, 2017 at 1:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
Can I suggest you send out another build before you go GA.
I for one have outstanding issues that were not in 1.3 (see previous emails).
I know you said you don’t have my issues on your install but that doesn’t mean they don’t exist.
Happy to test
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:11
To: McDonaldR
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <McDonaldR@angus.gov.uk> wrote:
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Thanks - this should be fixed for GA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Yes!
Installed quickly.
Splash screen to gui window about 7 secs and then another few secs to usable.
Much more responsive.
Expanding elements in tree is snappy.
I’ll test it some more tomorrow with connections to a production database.
Ross
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:52
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
The candidate build can be found at https://developer.pgadmin.org/~dpage/1.6/.
Note that as the timing is coupled with the PostgreSQL 10b2 release, we'll only rewrap now for showstopper issues, not anything minor.
On Tue, Jul 11, 2017 at 1:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
Can I suggest you send out another build before you go GA.
I for one have outstanding issues that were not in 1.3 (see previous emails).
I know you said you don’t have my issues on your install but that doesn’t mean they don’t exist.
Happy to test
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:11
To: McDonaldR
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <McDonaldR@angus.gov.uk> wrote:
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Thanks - this should be fixed for GA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
This message is strictly confidential. If you have received this in error, please inform the sender and remove it from your system. If received in error you may not copy, print, forward or use it or any attachment in any way. This message is not capable of creating a legal contract or a binding representation and does not represent the views of Angus Council. Emails may be monitored for security and network management reasons. Messages containing inappropriate content may be intercepted. Angus Council does not accept any liability for any harm that may be caused to the recipient system or data on it by this message or any attachment.
Yes!
Installed quickly.
Splash screen to gui window about 7 secs and then another few secs to usable.
Much more responsive.
Expanding elements in tree is snappy.
I’ll test it some more tomorrow with connections to a production database.
Ross
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:52
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
The candidate build can be found at https://developer.pgadmin.org/~dpage/1.6/.
Note that as the timing is coupled with the PostgreSQL 10b2 release, we'll only rewrap now for showstopper issues, not anything minor.
On Tue, Jul 11, 2017 at 1:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
Can I suggest you send out another build before you go GA.
I for one have outstanding issues that were not in 1.3 (see previous emails).
I know you said you don’t have my issues on your install but that doesn’t mean they don’t exist.
Happy to test
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:11
To: McDonaldR
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <McDonaldR@angus.gov.uk> wrote:
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Thanks - this should be fixed for GA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
This message is strictly confidential. If you have received this in error, please inform the sender and remove it from your system. If received in error you may not copy, print, forward or use it or any attachment in any way. This message is not capable of creating a legal contract or a binding representation and does not represent the views of Angus Council. Emails may be monitored for security and network management reasons. Messages containing inappropriate content may be intercepted. Angus Council does not accept any liability for any harm that may be caused to the recipient system or data on it by this message or any attachment.
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Yes!
Installed quickly.
Splash screen to gui window about 7 secs and then another few secs to usable.
Much more responsive.
Expanding elements in tree is snappy.
I’ll test it some more tomorrow with connections to a production database.
Ross
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:52
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
The candidate build can be found at https://developer.pgadmin.
org/~dpage/1.6/.
Note that as the timing is coupled with the PostgreSQL 10b2 release, we'll only rewrap now for showstopper issues, not anything minor.
On Tue, Jul 11, 2017 at 1:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
Can I suggest you send out another build before you go GA.
I for one have outstanding issues that were not in 1.3 (see previous emails).
I know you said you don’t have my issues on your install but that doesn’t mean they don’t exist.
Happy to test
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:11
To: McDonaldR
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <McDonaldR@angus.gov.uk> wrote:
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\
Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\
pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Thanks - this should be fixed for GA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL CompanyThis message is strictly confidential. If you have received this in error, please inform the sender and remove it from your system. If received in error you may not copy, print, forward or use it or any attachment in any way. This message is not capable of creating a legal contract or a binding representation and does not represent the views of Angus Council. Emails may be monitored for security and network management reasons. Messages containing inappropriate content may be intercepted. Angus Council does not accept any liability for any harm that may be caused to the recipient system or data on it by this message or any attachment.
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Yes!
Installed quickly.
Splash screen to gui window about 7 secs and then another few secs to usable.
Much more responsive.
Expanding elements in tree is snappy.
I’ll test it some more tomorrow with connections to a production database.
Ross
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:52
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
The candidate build can be found at https://developer.pgadmin.
org/~dpage/1.6/.
Note that as the timing is coupled with the PostgreSQL 10b2 release, we'll only rewrap now for showstopper issues, not anything minor.
On Tue, Jul 11, 2017 at 1:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
Can I suggest you send out another build before you go GA.
I for one have outstanding issues that were not in 1.3 (see previous emails).
I know you said you don’t have my issues on your install but that doesn’t mean they don’t exist.
Happy to test
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 13:11
To: McDonaldR
Cc: pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 10:03 AM, McDonaldR <McDonaldR@angus.gov.uk> wrote:
Hi Dave,
I’m testing the latest build (10/7/2017) from your download page.
I had a v1.5 build that fixed issues with the proxy server. It took ~30 secs from start to usable. Before that I could only run the v1.3 release.
This new build starts in about 9 seconds showing the splash screen and then it crashes with a Fatal Error: The application server could not be contacted.
There is nothing in the Event Viewer logs and the pgAdmin log is empty in C:\Users\username\AppData\
Roaming\pgAdmin
The registry key in HKEY_CURRENT_USER\Software\
pgadmin\pgadmin4 is blank with a value not set.
Windows 7 Enterprise 64 bit
16GB RAM
SSD
Behind the corporate proxy and firewall
Thanks - this should be fixed for GA.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL CompanyThis message is strictly confidential. If you have received this in error, please inform the sender and remove it from your system. If received in error you may not copy, print, forward or use it or any attachment in any way. This message is not capable of creating a legal contract or a binding representation and does not represent the views of Angus Council. Emails may be monitored for security and network management reasons. Messages containing inappropriate content may be intercepted. Angus Council does not accept any liability for any harm that may be caused to the recipient system or data on it by this message or any attachment.
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
> Try pressing Ctrl 0 (Control zero)
Yes that did it.
I also needed to reset layout for it to stick.
Start-up time still 25 secs to dash board so still slow for me (sorry but it’s a fact).
For comparison Server install start up is 5 seconds to dash board.
1. Does the desktop support GSSAPI. It doesn’t seem to work for me (I get error FATAL: GSSAPI authentication failed for user "postgres"). Server install works fine.
2. Did you webpack all the things for 1.6?
3. Will there be a web install package.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 15:43
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 2:47 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
Try pressing Ctrl 0 (Control zero) to reset the zoom level. The experimental ActiveQt build used a different scaling factor for the zoom which may have been saved in the registry. I found that on my machine - it had zoomed in so far that I just had a few pixels expanded to fit the screen.
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Hard to see what though, if it's not the zoom. I have tested on Windows 7 as well as Windows 10, so it *should* work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
> Try pressing Ctrl 0 (Control zero)
Yes that did it.
I also needed to reset layout for it to stick.
Start-up time still 25 secs to dash board so still slow for me (sorry but it’s a fact).
For comparison Server install start up is 5 seconds to dash board.
1. Does the desktop support GSSAPI. It doesn’t seem to work for me (I get error FATAL: GSSAPI authentication failed for user "postgres"). Server install works fine.
2. Did you webpack all the things for 1.6?
3. Will there be a web install package.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 15:43
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 2:47 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
Try pressing Ctrl 0 (Control zero) to reset the zoom level. The experimental ActiveQt build used a different scaling factor for the zoom which may have been saved in the registry. I found that on my machine - it had zoomed in so far that I just had a few pixels expanded to fit the screen.
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Hard to see what though, if it's not the zoom. I have tested on Windows 7 as well as Windows 10, so it *should* work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
> Try pressing Ctrl 0 (Control zero)
Yes that did it.
I also needed to reset layout for it to stick.
Start-up time still 25 secs to dash board so still slow for me (sorry but it’s a fact).
For comparison Server install start up is 5 seconds to dash board.
1. Does the desktop support GSSAPI. It doesn’t seem to work for me (I get error FATAL: GSSAPI authentication failed for user "postgres"). Server install works fine.
2. Did you webpack all the things for 1.6?
3. Will there be a web install package.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 15:43
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 2:47 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
Try pressing Ctrl 0 (Control zero) to reset the zoom level. The experimental ActiveQt build used a different scaling factor for the zoom which may have been saved in the registry. I found that on my machine - it had zoomed in so far that I just had a few pixels expanded to fit the screen.
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Hard to see what though, if it's not the zoom. I have tested on Windows 7 as well as Windows 10, so it *should* work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
> Try pressing Ctrl 0 (Control zero)
Yes that did it.
I also needed to reset layout for it to stick.
Start-up time still 25 secs to dash board so still slow for me (sorry but it’s a fact).
For comparison Server install start up is 5 seconds to dash board.
1. Does the desktop support GSSAPI. It doesn’t seem to work for me (I get error FATAL: GSSAPI authentication failed for user "postgres"). Server install works fine.
2. Did you webpack all the things for 1.6?
3. Will there be a web install package.
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 15:43
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 2:47 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
Try pressing Ctrl 0 (Control zero) to reset the zoom level. The experimental ActiveQt build used a different scaling factor for the zoom which may have been saved in the registry. I found that on my machine - it had zoomed in so far that I just had a few pixels expanded to fit the screen.
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Hard to see what though, if it's not the zoom. I have tested on Windows 7 as well as Windows 10, so it *should* work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
>No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as >well as hostname/address which many people need with Kerberos for example.
Not sure I understand this.
Windows works fine with gssapi (the server is on a linux box).
I make gssapi connections all the time with npgsql library and the web version of pgadmin and terminal software so I don’t have to use passwords.
It just doesn’t seem to work with the desktop version of pgadmin.
>Before Webpack patch:-
>It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
So Neel also gets 20 second start up (before webpack) . At least it’s not just me. I look forward to having those 7 secs.
On a more positive note I do find the browsing of nodes and retrieving table SQL seems to be snappier in 1.6.
>Will there be a web install package.
What I meant was will there be a pgadmin4-v1-web package update.
Oh and as an aside I think you made the right decision going with a web app. It’s definitely the future .
After these performance problems have been addressed.
It’s not easy creating a feature rich web app and I appreciate all the work you guys have done on this.
Just keep an open mind that your end users may have issues you don’t. There are so many environmental factors to consider.
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 16:36
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
On Tue, Jul 11, 2017 at 4:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
> Try pressing Ctrl 0 (Control zero)
Yes that did it.
I also needed to reset layout for it to stick.
OK, good.
Start-up time still 25 secs to dash board so still slow for me (sorry but it’s a fact).
For comparison Server install start up is 5 seconds to dash board.
Hmm, that is still slow. I get about 11 seconds on Windows 10, running on VMware on my MacBook Pro. Any AV software etc. that may be slowing things?
1. Does the desktop support GSSAPI. It doesn’t seem to work for me (I get error FATAL: GSSAPI authentication failed for user "postgres"). Server install works fine.
No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as well as hostname/address which many people need with Kerberos for example.
2. Did you webpack all the things for 1.6?
No, unfortunately the patch wasn't ready. I have a WIP version, and it's looking good; Neel reported the following using the runtime you have:
Before Webpack patch:-
It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
After Webpack patch:-
It took ~13 seconds ( timing of python server start + page load ).
We got ~7 seconds improvement with webpack on same machine & same Qt configuration and this will be useful in windows performance issue as well :)
I expect this to be in 1.7, which we'll aim to get out fairly quickly (vacations allowing)
3. Will there be a web install package.
There is a source tarball and Python wheel available at http://developer.pgadmin.org/~dpage/1.6/
Thanks!
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 15:43
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 2:47 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
Try pressing Ctrl 0 (Control zero) to reset the zoom level. The experimental ActiveQt build used a different scaling factor for the zoom which may have been saved in the registry. I found that on my machine - it had zoomed in so far that I just had a few pixels expanded to fit the screen.
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Hard to see what though, if it's not the zoom. I have tested on Windows 7 as well as Windows 10, so it *should* work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
>No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as >well as hostname/address which many people need with Kerberos for example.
Not sure I understand this.
Windows works fine with gssapi (the server is on a linux box).
I make gssapi connections all the time with npgsql library and the web version of pgadmin and terminal software so I don’t have to use passwords.
It just doesn’t seem to work with the desktop version of pgadmin.
>Before Webpack patch:-
>It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
So Neel also gets 20 second start up (before webpack) . At least it’s not just me. I look forward to having those 7 secs.
On a more positive note I do find the browsing of nodes and retrieving table SQL seems to be snappier in 1.6.
>Will there be a web install package.
What I meant was will there be a pgadmin4-v1-web package update.
Oh and as an aside I think you made the right decision going with a web app. It’s definitely the future .
After these performance problems have been addressed.
It’s not easy creating a feature rich web app and I appreciate all the work you guys have done on this.
Just keep an open mind that your end users may have issues you don’t. There are so many environmental factors to consider.
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 16:36
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
On Tue, Jul 11, 2017 at 4:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
> Try pressing Ctrl 0 (Control zero)
Yes that did it.
I also needed to reset layout for it to stick.
OK, good.
Start-up time still 25 secs to dash board so still slow for me (sorry but it’s a fact).
For comparison Server install start up is 5 seconds to dash board.
Hmm, that is still slow. I get about 11 seconds on Windows 10, running on VMware on my MacBook Pro. Any AV software etc. that may be slowing things?
1. Does the desktop support GSSAPI. It doesn’t seem to work for me (I get error FATAL: GSSAPI authentication failed for user "postgres"). Server install works fine.
No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as well as hostname/address which many people need with Kerberos for example.
2. Did you webpack all the things for 1.6?
No, unfortunately the patch wasn't ready. I have a WIP version, and it's looking good; Neel reported the following using the runtime you have:
Before Webpack patch:-
It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
After Webpack patch:-
It took ~13 seconds ( timing of python server start + page load ).
We got ~7 seconds improvement with webpack on same machine & same Qt configuration and this will be useful in windows performance issue as well :)
I expect this to be in 1.7, which we'll aim to get out fairly quickly (vacations allowing)
3. Will there be a web install package.
There is a source tarball and Python wheel available at http://developer.pgadmin.org/~dpage/1.6/
Thanks!
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 15:43
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 2:47 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
Try pressing Ctrl 0 (Control zero) to reset the zoom level. The experimental ActiveQt build used a different scaling factor for the zoom which may have been saved in the registry. I found that on my machine - it had zoomed in so far that I just had a few pixels expanded to fit the screen.
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Hard to see what though, if it's not the zoom. I have tested on Windows 7 as well as Windows 10, so it *should* work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
>No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as >well as hostname/address which many people need with Kerberos for example.
Not sure I understand this.
Windows works fine with gssapi (the server is on a linux box).
I make gssapi connections all the time with npgsql library and the web version of pgadmin and terminal software so I don’t have to use passwords.
It just doesn’t seem to work with the desktop version of pgadmin.
>Before Webpack patch:-
>It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
So Neel also gets 20 second start up (before webpack) . At least it’s not just me. I look forward to having those 7 secs.
On a more positive note I do find the browsing of nodes and retrieving table SQL seems to be snappier in 1.6.
>Will there be a web install package.
What I meant was will there be a pgadmin4-v1-web package update.
Oh and as an aside I think you made the right decision going with a web app. It’s definitely the future .
After these performance problems have been addressed.
It’s not easy creating a feature rich web app and I appreciate all the work you guys have done on this.
Just keep an open mind that your end users may have issues you don’t. There are so many environmental factors to consider.
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 16:36
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
On Tue, Jul 11, 2017 at 4:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
> Try pressing Ctrl 0 (Control zero)
Yes that did it.
I also needed to reset layout for it to stick.
OK, good.
Start-up time still 25 secs to dash board so still slow for me (sorry but it’s a fact).
For comparison Server install start up is 5 seconds to dash board.
Hmm, that is still slow. I get about 11 seconds on Windows 10, running on VMware on my MacBook Pro. Any AV software etc. that may be slowing things?
1. Does the desktop support GSSAPI. It doesn’t seem to work for me (I get error FATAL: GSSAPI authentication failed for user "postgres"). Server install works fine.
No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as well as hostname/address which many people need with Kerberos for example.
2. Did you webpack all the things for 1.6?
No, unfortunately the patch wasn't ready. I have a WIP version, and it's looking good; Neel reported the following using the runtime you have:
Before Webpack patch:-
It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
After Webpack patch:-
It took ~13 seconds ( timing of python server start + page load ).
We got ~7 seconds improvement with webpack on same machine & same Qt configuration and this will be useful in windows performance issue as well :)
I expect this to be in 1.7, which we'll aim to get out fairly quickly (vacations allowing)
3. Will there be a web install package.
There is a source tarball and Python wheel available at http://developer.pgadmin.org/~
dpage/1.6/
Thanks!
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 15:43
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 2:47 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
Try pressing Ctrl 0 (Control zero) to reset the zoom level. The experimental ActiveQt build used a different scaling factor for the zoom which may have been saved in the registry. I found that on my machine - it had zoomed in so far that I just had a few pixels expanded to fit the screen.
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Hard to see what though, if it's not the zoom. I have tested on Windows 7 as well as Windows 10, so it *should* work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
>No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as >well as hostname/address which many people need with Kerberos for example.
Not sure I understand this.
Windows works fine with gssapi (the server is on a linux box).
I make gssapi connections all the time with npgsql library and the web version of pgadmin and terminal software so I don’t have to use passwords.
It just doesn’t seem to work with the desktop version of pgadmin.
>Before Webpack patch:-
>It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
So Neel also gets 20 second start up (before webpack) . At least it’s not just me. I look forward to having those 7 secs.
On a more positive note I do find the browsing of nodes and retrieving table SQL seems to be snappier in 1.6.
>Will there be a web install package.
What I meant was will there be a pgadmin4-v1-web package update.
Oh and as an aside I think you made the right decision going with a web app. It’s definitely the future .
After these performance problems have been addressed.
It’s not easy creating a feature rich web app and I appreciate all the work you guys have done on this.
Just keep an open mind that your end users may have issues you don’t. There are so many environmental factors to consider.
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 16:36
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
On Tue, Jul 11, 2017 at 4:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
> Try pressing Ctrl 0 (Control zero)
Yes that did it.
I also needed to reset layout for it to stick.
OK, good.
Start-up time still 25 secs to dash board so still slow for me (sorry but it’s a fact).
For comparison Server install start up is 5 seconds to dash board.
Hmm, that is still slow. I get about 11 seconds on Windows 10, running on VMware on my MacBook Pro. Any AV software etc. that may be slowing things?
1. Does the desktop support GSSAPI. It doesn’t seem to work for me (I get error FATAL: GSSAPI authentication failed for user "postgres"). Server install works fine.
No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as well as hostname/address which many people need with Kerberos for example.
2. Did you webpack all the things for 1.6?
No, unfortunately the patch wasn't ready. I have a WIP version, and it's looking good; Neel reported the following using the runtime you have:
Before Webpack patch:-
It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
After Webpack patch:-
It took ~13 seconds ( timing of python server start + page load ).
We got ~7 seconds improvement with webpack on same machine & same Qt configuration and this will be useful in windows performance issue as well :)
I expect this to be in 1.7, which we'll aim to get out fairly quickly (vacations allowing)
3. Will there be a web install package.
There is a source tarball and Python wheel available at http://developer.pgadmin.org/~
dpage/1.6/
Thanks!
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 15:43
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 2:47 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
Try pressing Ctrl 0 (Control zero) to reset the zoom level. The experimental ActiveQt build used a different scaling factor for the zoom which may have been saved in the registry. I found that on my machine - it had zoomed in so far that I just had a few pixels expanded to fit the screen.
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Hard to see what though, if it's not the zoom. I have tested on Windows 7 as well as Windows 10, so it *should* work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Tue, Jul 11, 2017 at 4:56 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:>No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as >well as hostname/address which many people need with Kerberos for example.
Not sure I understand this.
Windows works fine with gssapi (the server is on a linux box).
I make gssapi connections all the time with npgsql library and the web version of pgadmin and terminal software so I don’t have to use passwords.
It just doesn’t seem to work with the desktop version of pgadmin.
We rely entirely on libpq to handle this side of things, which means we're reliant on how it was built on a particular platform. On Windows, GSSAPI was dropped in favour of SSPI many years ago. I'm not familiar with either though, so I can't say what will or won't work - just that if it works with libpq on Windows, it should work with pgAdmin.
>Before Webpack patch:-
>It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
So Neel also gets 20 second start up (before webpack) . At least it’s not just me. I look forward to having those 7 secs.
He is on a virtual machine though.
On a more positive note I do find the browsing of nodes and retrieving table SQL seems to be snappier in 1.6.
Yes, I've found that. As it turns out, we're actually not using the ActiveQT port that Neel worked on. It looks like Qt (or the fork of QtWebKit we use) fixed the underlying issue.
>Will there be a web install package.
What I meant was will there be a pgadmin4-v1-web package update.
Oh, right - yeah, Devrim was working on that earlier today.
Oh and as an aside I think you made the right decision going with a web app. It’s definitely the future .
After these performance problems have been addressed.
It’s not easy creating a feature rich web app and I appreciate all the work you guys have done on this.
Thank you.
Just keep an open mind that your end users may have issues you don’t. There are so many environmental factors to consider.
Oh, after over 20 years in IT support and software development, I've become painfully aware of that :-).
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 16:36
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
On Tue, Jul 11, 2017 at 4:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
> Try pressing Ctrl 0 (Control zero)
Yes that did it.
I also needed to reset layout for it to stick.
OK, good.
Start-up time still 25 secs to dash board so still slow for me (sorry but it’s a fact).
For comparison Server install start up is 5 seconds to dash board.
Hmm, that is still slow. I get about 11 seconds on Windows 10, running on VMware on my MacBook Pro. Any AV software etc. that may be slowing things?
1. Does the desktop support GSSAPI. It doesn’t seem to work for me (I get error FATAL: GSSAPI authentication failed for user "postgres"). Server install works fine.
No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as well as hostname/address which many people need with Kerberos for example.
2. Did you webpack all the things for 1.6?
No, unfortunately the patch wasn't ready. I have a WIP version, and it's looking good; Neel reported the following using the runtime you have:
Before Webpack patch:-
It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
After Webpack patch:-
It took ~13 seconds ( timing of python server start + page load ).
We got ~7 seconds improvement with webpack on same machine & same Qt configuration and this will be useful in windows performance issue as well :)
I expect this to be in 1.7, which we'll aim to get out fairly quickly (vacations allowing)
3. Will there be a web install package.
There is a source tarball and Python wheel available at http://developer.pgadmin.org/~
dpage/1.6/
Thanks!
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 15:43
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 2:47 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
Try pressing Ctrl 0 (Control zero) to reset the zoom level. The experimental ActiveQt build used a different scaling factor for the zoom which may have been saved in the registry. I found that on my machine - it had zoomed in so far that I just had a few pixels expanded to fit the screen.
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Hard to see what though, if it's not the zoom. I have tested on Windows 7 as well as Windows 10, so it *should* work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company--Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Tue, Jul 11, 2017 at 4:56 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:>No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as >well as hostname/address which many people need with Kerberos for example.
Not sure I understand this.
Windows works fine with gssapi (the server is on a linux box).
I make gssapi connections all the time with npgsql library and the web version of pgadmin and terminal software so I don’t have to use passwords.
It just doesn’t seem to work with the desktop version of pgadmin.
We rely entirely on libpq to handle this side of things, which means we're reliant on how it was built on a particular platform. On Windows, GSSAPI was dropped in favour of SSPI many years ago. I'm not familiar with either though, so I can't say what will or won't work - just that if it works with libpq on Windows, it should work with pgAdmin.
>Before Webpack patch:-
>It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
So Neel also gets 20 second start up (before webpack) . At least it’s not just me. I look forward to having those 7 secs.
He is on a virtual machine though.
On a more positive note I do find the browsing of nodes and retrieving table SQL seems to be snappier in 1.6.
Yes, I've found that. As it turns out, we're actually not using the ActiveQT port that Neel worked on. It looks like Qt (or the fork of QtWebKit we use) fixed the underlying issue.
>Will there be a web install package.
What I meant was will there be a pgadmin4-v1-web package update.
Oh, right - yeah, Devrim was working on that earlier today.
Oh and as an aside I think you made the right decision going with a web app. It’s definitely the future .
After these performance problems have been addressed.
It’s not easy creating a feature rich web app and I appreciate all the work you guys have done on this.
Thank you.
Just keep an open mind that your end users may have issues you don’t. There are so many environmental factors to consider.
Oh, after over 20 years in IT support and software development, I've become painfully aware of that :-).
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 16:36
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
On Tue, Jul 11, 2017 at 4:14 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
> Try pressing Ctrl 0 (Control zero)
Yes that did it.
I also needed to reset layout for it to stick.
OK, good.
Start-up time still 25 secs to dash board so still slow for me (sorry but it’s a fact).
For comparison Server install start up is 5 seconds to dash board.
Hmm, that is still slow. I get about 11 seconds on Windows 10, running on VMware on my MacBook Pro. Any AV software etc. that may be slowing things?
1. Does the desktop support GSSAPI. It doesn’t seem to work for me (I get error FATAL: GSSAPI authentication failed for user "postgres"). Server install works fine.
No - PostgreSQL builds on Windows dropped GSSAPI in favour of SSPI some years ago. That functionality is provided by the underlying libpq, not pgAdmin - though pgAdmin 1.6 does allow you to specify the host address as well as hostname/address which many people need with Kerberos for example.
2. Did you webpack all the things for 1.6?
No, unfortunately the patch wasn't ready. I have a WIP version, and it's looking good; Neel reported the following using the runtime you have:
Before Webpack patch:-
It took ~20 seconds. This 20 seconds includes when user double click on application ( timing of python server start + page load )
After Webpack patch:-
It took ~13 seconds ( timing of python server start + page load ).
We got ~7 seconds improvement with webpack on same machine & same Qt configuration and this will be useful in windows performance issue as well :)
I expect this to be in 1.7, which we'll aim to get out fairly quickly (vacations allowing)
3. Will there be a web install package.
There is a source tarball and Python wheel available at http://developer.pgadmin.org/~
dpage/1.6/
Thanks!
Thanks
Mike
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: 11 July 2017 15:43
To: Mike Surcouf
Cc: McDonaldR; pgadmin-hackers; pgAdmin Support
Subject: Re: Windows testing required: Updated runtime
Hi
On Tue, Jul 11, 2017 at 2:47 PM, Mike Surcouf <mikes@surcouf.co.uk> wrote:
Hi Dave
v1.6
Show splash then backround of main window then hangs forever. pgadmin4.log is 0 bytes
Try pressing Ctrl 0 (Control zero) to reset the zoom level. The experimental ActiveQt build used a different scaling factor for the zoom which may have been saved in the registry. I found that on my machine - it had zoomed in so far that I just had a few pixels expanded to fit the screen.
v1.3
Uninstalled then reinstalled 1.3 (which was the last version that worked).and all is ok again
But I guess it works on your machine so it must be something wrong with my setup
Hard to see what though, if it's not the zoom. I have tested on Windows 7 as well as Windows 10, so it *should* work.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company--Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company