RE: Windows testing required: Updated runtime
| От | McDonaldR |
|---|---|
| Тема | RE: Windows testing required: Updated runtime |
| Дата | |
| Msg-id | 7CCEF44D1C42854999B19B1EB27281F6834DCF39@SR2ORBHQ2K803.angus.gov.uk обсуждение исходный текст |
| Ответ на | Re: Windows testing required: Updated runtime (Dave Page <dpage@pgadmin.org>) |
| Ответы |
Re: Windows testing required: Updated runtime
(Dave Page <dpage@pgadmin.org>)
Re: Windows testing required: Updated runtime (Dave Page <dpage@pgadmin.org>) |
| Список | pgadmin-hackers |
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.
Вложения
В списке pgadmin-hackers по дате отправления:
Следующее
От: Ashesh VashiДата:
Сообщение: Re: pgAdmin 4 commit: Revert "Ensure dependencies are packaged in the tarba