PostgreSQL Release of JDBC 42.5.3 and pgAdmin 4 v6.20
-
PostgreSQL JDBC 42.5.3 Released
The PostgreSQL JDBC Project is pleased to announce the release of version 42.5.3 which includes the changes for 42.5.2 as well as fixing the regressions.
This release fixes 2 regressions which were introduced in 42.5.2
We recommend not using 42.5.2
Notable changes for 42.5.2:
- Define binary transfer for custom types dynamically/automatically.
- Added gssResponseTimeout to make sure we don’t wait forever on a GSS RESPONSE
- Make sure socket is closed if an exception is thrown in createSocket
- Fix hanging ssl connections
- Fix binary conversion of (very) long numeric values (longer than 4 * 2^15 digits)
-
pgAdmin 4 v6.20 Released
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.
Note
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.