Re: Windows testing required: Updated runtime

From: Dave Page <dpage(at)pgadmin(dot)org>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, pgAdmin Support <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Windows testing required: Updated runtime
Date: 2017-07-07 08:45:34
Message-ID: CA+OCxoxu4okpLux907eKojsttxCy9VZBMGAaH12pVgM83Jdasw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers pgadmin-support

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(at)pgadmin(dot)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

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Mike Surcouf 2017-07-07 09:17:02 RE: Windows testing required: Updated runtime
Previous Message Dave Page 2017-07-07 08:38:54 Re: Windows testing required: Updated runtime

Browse pgadmin-support by date

  From Date Subject
Next Message Mike Surcouf 2017-07-07 09:17:02 RE: Windows testing required: Updated runtime
Previous Message Dave Page 2017-07-07 08:38:54 Re: Windows testing required: Updated runtime