The pgAdmin Development Team is pleased to announce pgAdmin 4 version 6.20. This release of pgAdmin 4 includes 18 bug fixes and new features. For more details please see the release notes.
pgAdmin is the leading Open Source graphical management tool for PostgreSQL. For more information, please see the website.
Whilst pgAdmin 4 does not formally support downgrading, it typically does work if you uninstall and then reinstall the application.
This release of pgAdmin includes a major change to the configuration database structure which is NOT backward compatible, and therefore a straightforward downgrade will not work.
If you are using the default SQLite database for your configuration (as will be the case for the vast majority of users), the old version of the configuration database will be backed up to "pgadmin4.db.prev.bak" in your storage directory. If you wish to downgrade to pgAdmin v6.19 or earlier, after running v6.20, you must restore this file to "pgadmin4.db" in the same directory, BEFORE starting the older version of pgAdmin again.
If you are storing your configuration in an external PostgreSQL database, you will need to restore a backup of that database taken prior to the upgrade to v6.20, if you wish to return to the earlier version.
Changes made after migration such as the addition of new servers, will not be stored in the old database and will have to be re-created following a downgrade.
Notable changes in this release include:
Added support for setting PostgreSQL connection parameters.
With the help of this feature, a user can specify the connection parameters when connecting to a server using the server dialog. In the server dialog, we have added a new Parameters tab and removed the SSL tab. The Parameters tab now contains all SSL tab controls.
Builds for Windows and macOS are available now, along with a Python Wheel, Docker Container, RPM, DEB Package, and source code tarball from the tarball area.