Noteworthy improvements include the option to load or replace the servers.json file during container startup and the introduction of a dedicated user management tab to streamline the interface. Additionally, the release addresses multiple security vulnerabilities, including XSS and remote code execution issues, as well as several bugs related to the Query Tool and performance on macOS 15.4.
Other enhancements involve user interface improvements, such as displaying tooltips for disabled icon buttons and ensuring modal dialogs are not triggered multiple times. The development team has also fixed issues related to data grid behavior in the Query Tool and adjustments necessary for compatibility with Python 3.13.
The builds for Windows and macOS, along with other distribution formats such as Python Wheel, Docker Container, RPM, DEB Package, and source code tarball, are currently available for download.
Looking forward, pgAdmin continues to evolve as the leading open-source graphical management tool for PostgreSQL, promising ongoing enhancements and user-focused features in future releases. As the community grows, users can anticipate more robust functionality and improved security measures, ensuring a reliable and efficient database management experience
pgAdmin 4 9.2 released
The pgAdmin Development Team has announced the release of pgAdmin 4 v9.2, featuring 24 bug fixes and new enhancements. The update introduces features including the ability to configure font families for SQL editors, automatic file opening, execution of SQL commands post-connection, restoration of plain SQL database dumps, and the creation of directory nodes in EPAS. The functionality encompasses an option to load or replace the servers.json file upon container startup, as well as a dedicated tab for user management. The release also resolves issues including XSS vulnerabilities, remote code execution concerns, and problems related to the Query Tool and Cloud Deployment. The update also resolves issues related to the query tool crashing on macOS 15.4 and the upgrade_check API returning an unexpected keyword argument.
