Postgres Pro
Downloads
Home   >   mailing lists

Re: pgAdmin 4 v5.1 Released - Mailing list pgadmin-support

From Dave Caughey
Subject Re: pgAdmin 4 v5.1 Released
Date
Msg-id CAAj2gHziica14+XASVu7kuRnK77K489pNxYA3w1JbJjkp51PWg@mail.gmail.com
Whole thread Raw
In response to pgAdmin 4 v5.1 Released  (Akshay Joshi <akshay.joshi@enterprisedb.com>)
Responses Re: pgAdmin 4 v5.1 Released  (Dave Page <dpage@pgadmin.org>)
List pgadmin-support
Tree view
Hi all,

Normally, there's always been a little pop-up when launching pgAdmin that says that there's a new version, available.

When I saw the v5.1 release announcement email, I launched pgAdmin v5.0, saw the new version popup, clicked on it and a new window opened with the landing page where I would be able to pick the platform I needed (e.g., Windows).  But then, relying on old habits developed when pgAdmin ran in the browser, I closed the pgAdmin window... and the landing page window closed, too.

So I relaunched pgAdmin, but now I don't get any message about version 5.1 being available (I'm still running v5.0), nor can I find a "check for updates" option in the menus (it could be I'm simply being obtuse, and missing an obvious option!)

Ultimately, I solved the problem by browsing to pgadmin.org, but is it really the design intent that the upgrade message only shows up once, ever, rather than each time you launch pgAdmin?   Or perhaps give a "check for updates" option under any tips on how I can update pgAdmin?  And, running the installer that I manually downloaded, gave a message that a bunch of nwjs processes need to be closed, but selecting the "close automatically" option failed, and offered me the option to retry (which failed again).   Ultimately, I noticed a background window on the taskbar that said that pgAdmin couldn't contact the server, and upon closing that window, was able to re-attempt to upgrade, whereupon it did appear to update (at least, Help says I'm running 5.1, now)

So methinks there's a few assumptions being made that things proceeded correctly, with no contingency for when don't... e.g., was the fact that I wasn't getting an update available message tied to the fact that there was some underlying problem?  Did that fact that there was a background window complaining that the server couldn't be contact result in nwjs being uncloseable?   I can raise a RM if you'd like, but I'm going to guess that I won't be able to provide a reproducible test case...

Cheers,
Dave


On Thu, Mar 25, 2021 at 8:31 AM Akshay Joshi <akshay.joshi@enterprisedb.com> wrote:

The pgAdmin Development Team is pleased to announce pgAdmin 4 version 5.1.

This release of pgAdmin 4 includes 42 bug fixes and new features. For more details please see the release notes at:

    https://www.pgadmin.org/docs/pgadmin4/5.1/release_notes_5_1.html.

pgAdmin is the leading Open Source graphical management tool for PostgreSQL. For more information, please see:

    https://www.pgadmin.org/

Notable changes in this release include:

Features:

  • Zoom scaling options with keyboard shortcuts in runtime:

This feature includes the zoom scaling (Zoom In, Zoom Out, Actual Size) options along with Enter/Exit Full-Screen mode. We have added the options in Menu as well as using keyboard shortcuts users can perform the desired operation.

  • Show the login roles that are members of a group role be shown when examining a group role.

  • Added '--replace' option in Import server to replace the list of servers with the newly imported one.

  • Make the container distribution a multi-arch build with x86_64 and Arm64 support.

  • Make 'Kerberos an optional feature in the Python wheel, to avoid the need to install MIT Kerberos on the system by default.

Bugs/Housekeeping:

  • Fixed an issue where hanging symlinks in a directory caused the select file dialog to break.

  • Make the 'Save Data Changes' icon to be more intuitive.

  • Ensure that cell content being auto-selected when editing the cell data.

  • Ensure that SQL formatter should not add extra tabs and format the SQL correctly.

  • Ensure that SQL formatter should not use tab size if 'Use spaces?' set to false.

  • Fixed encoding issue when database encoding set to SQL_ASCII and name of the column is in ASCII character.

  • Ensure that the user should be able to kill the session from Dashboard if the user has a 'pg_signal_backend' role.

  • Ensure PGADMIN_DEFAULT_EMAIL looks sane when initializing a container deployment.

  • Fixed an issue where the user is not able to change the connection in Query Tool when any SQL file is opened.

  • Fixed an issue where copy/paste rows in view data paste the wrong value for boolean type.

  • Ensure that toggle buttons are accessible by most screen readers.

Builds for Windows and macOS are available now, along with a Python Wheel,
Docker Container, RPM, DEB Package, and source code tarball from:

--
Akshay Joshi
pgAdmin Project

pgadmin-support by date:

Previous
From: androxkentaki
Date:
Subject: Re: pgAdmin 4 v5.1 Released
Next
From: Dave Page
Date:
Subject: Re: pgAdmin 4 v5.1 Released