pgAdmin 4 v9.12 adds INHERIT and SET checkboxes to the role membership tab and a toolbar button that pulls the full result set in the query tool, making role management and large data exports easier. OAuth2/OIDC authentication now has better claim handling and extra configuration fields for providers such as Azure AD or Keycloak. Important bug fixes include a patch for the dashboard freeze when many locks are present, secret‑key masking to address CVE‑2026‑1707, clearer pg_restore logs, and a Mac OS auto‑update fix on read‑only volumes. If any of these features or stability improvements match your workflow, upgrading now is the sensible move.

pgAdmin 4 v9.12: What’s New and Which Fixes Actually Matter

pgAdmin 4 v9.12 just landed, and you can download it from the official site. In this quick rundown I’ll point out the three headline features that could change how you work with roles and queries, then flag the bug fixes that are worth a restart versus the ones you can ignore. If you’ve been putting off the upgrade because “it looks like another fluff release,” read on.

Role Membership UI Gets INHERIT and SET

The role editor’s membership tab now shows checkboxes for INHERIT and SET. Administrators who create group roles often have to toggle these flags manually in SQL (ALTER ROLE … INHERIT). The new UI lets them do it with a mouse click, eliminating transcription errors and speeding up role provisioning.

Query Tool Can Pull the Whole Result Set

A fresh button on the query‑tool toolbar forces pgAdmin to fetch the complete result set regardless of any paging limit. This is handy when exporting thousands of rows to CSV or copying data into spreadsheets; the old “copy all” silently stopped at the first 1 000 rows, forcing users to scroll forever.

OAuth2 / OIDC Claims Handling Improves

OAuth2 and OpenID Connect authentication now expose more claim‑mapping options and finer‑grained configuration fields. Users who have been blocked by “missing scope” errors after a provider upgrade can now align custom claim names directly in the UI, avoiding the need to patch source code.

Bug Fixes That Actually Matter

• Dashboard freeze with many locks – On heavily loaded servers the dashboard used to hang when lock counts spiked. The fix lets the page render instantly, giving DBAs a usable view of lock activity.
• Secret key masking (CVE‑2026‑1707) – When restoring plain SQL files, the secret key now appears masked in the process watcher, preventing accidental credential leaks from screenshots.
• pg_restore log clarity – Logs now separate genuine restore failures from UI sync glitches, making troubleshooting far less confusing for support teams.
• Mac OS auto‑update on read‑only volumes – The updater no longer aborts when pgAdmin lives in a read‑only /Applications folder; updates apply smoothly.

Housekeeping Fixes You Might Not Notice

• Optimized checkbox selection logic in the backup dialog objects tree.
• Re‑encryption of saved shared server passwords after a password change.
• Sorting glitch fixed in the system stats memory usage table.
  These changes are good to have but won’t affect most users unless they run into those exact edge cases.

Full Change Log

Features

• Add new options like INHERIT and SET to the Role’s membership tab.
• Add a new button in the query tool data output toolbar to get entire range of data.
• Enhance OAUTH2 and OIDC authentication support with improved claims handling and configuration options.

Bugs / Housekeeping

• Mask the secret key for restrict option in the process watcher when restoring plain SQL file (CVE‑2026‑1707).
• Fix Query Tool state restoration for new connections and queries.
• Fix pg_restore logs to distinguish UI sync issues from actual failures.
• Optimize checkbox selection logic in backup dialog objects tree.
• Fixed an issue where double click to open a file in the file manager is not working.
• Ensure saved shared server passwords are re‑encrypted on password change.
• Fixed an issue where the dashboard freezes on initial render when there is a high number of locks.
• Fixed the SSL certificate issue while checking for the upgrade.
• Fixed a sorting issue in the system stats memory usage table.
• Disable Parameters and Membership fields when object is not new for Login and group roles.
• Fixed an issue where the Query History panel would auto‑scroll to the top and did not preserve the scroll bar position for the selected entry.
• Fixed an issue where pgAdmin4 app on macOS cannot auto‑update while running on a read‑only volume even if present in the Applications folder.
• Fixed an issue where connection parameters were using localized values instead of literal values, causing connection failures.
• Ensure the container deployment supports boolean values in yaml format.
• Fix pgAdmin fails when performing Backup/Restore on a PostgreSQL connection defined exclusively via pg_service.conf.

Should You Upgrade Now?

If any of the three new features line up with your workflow—especially the role INHERIT/SET UI or the full‑export button—it’s a no‑brainer. Even if you’re just after stability, the dashboard freeze fix alone is worth the jump on busy servers. For anyone who isn’t actively using OAuth2/OIDC, you could hold off a week and let the community vet the release, but there’s nothing dangerous about installing it today.

Give pgAdmin 4 v9.12 a spin; at worst you’ll get a cleaner UI, at best you’ll save yourself a few minutes of copy‑paste drudgery.