- Getting Started
- Connecting To A Server
- Managing Cluster Objects
- Managing Database Objects
- Creating or Modifying a Table
- Management Basics
- Backup and Restore
- Developer Tools
- pgAdmin Project Contributions
- Release Notes
- Version 6.3
- Version 6.2
- Version 6.1
- Version 6.0
- Version 5.7
- Version 5.6
- Version 5.5
- Version 5.4
- Version 5.3
- Version 5.2
- Version 5.1
- Version 5.0
- Version 4.30
- Version 4.29
- Version 4.28
- Version 4.27
- Version 4.26
- Version 4.25
- Version 4.24
- Version 4.23
- Version 4.22
- Version 4.21
- Version 4.20
- Version 4.19
- Version 4.18
- Version 4.17
- Version 4.16
- Version 4.15
- Version 4.14
- Version 4.13
- Version 4.12
- Version 4.11
- Version 4.10
- Version 4.9
- Version 4.8
- Version 4.7
- Version 4.6
- Version 4.5
- Version 4.4
- Version 4.3
- Version 4.2
- Version 4.1
- Version 4.0
- Version 3.6
- Version 3.5
- Version 3.4
- Version 3.3
- Version 3.2
- Version 3.1
- Version 3.0
- Version 2.1
- Version 2.0
- Version 1.6
- Version 1.5
- Version 1.4
- Version 1.3
- Version 1.2
- Version 1.1
- Version 1.0
Release date: 2020-07-23
This release contains a number of bug fixes and new features since the release of pgAdmin4 4.23.
Issue #5235 - Support configuration files that are external to the application installation.
Issue #5484 - Added support for LDAP authentication with different DN by setting the dedicated user for the LDAP connection.
Issue #5583 - Added support for schema level restriction.
Issue #5601 - Added RLS Policy support in Schema Diff.
Issue #5622 - Added support for permissive/restricted policy type while creating RLS Policy.
Issue #5650 - Added support for LDAP anonymous binding.
Issue #5653 - Added High Contrast theme support.
Issue #3814 - Fixed issue of error message not getting displayed when filename is empty for backup, restore, and import/export.
Issue #3851 - Add proper indentation to the code while generating functions, procedures, and trigger functions.
Issue #4235 - Fixed tab indent issue on a selection of lines is deleting the content when ‘use spaces == true’ in the preferences.
Issue #5137 - Fixed save button enable issue when focusing in and out of numeric input field.
Issue #5287 - Fixed dark theme-related CSS and modify the color codes.
Issue #5414 - Use QStandardPaths::AppLocalDataLocation in the runtime to determine where to store runtime logs.
Issue #5463 - Fixed an issue where CSV download quotes numeric columns.
Issue #5470 - Fixed backgrid row hover issue where on hover background color is set for edit and delete cell only.
Issue #5530 - Ensure that the referenced table should be displayed on foreign key constraints.
Issue #5554 - Replace the runtime themes with ones that don’t have sizing issues.
Issue #5569 - Fixed reverse engineered SQL for partitions when storage parameters are specified.
Issue #5577 - Include LICENSE and DEPENDENCIES [inventory] files in official packages.
Issue #5621 - Remove extra brackets from reverse engineering SQL of RLS Policy.
Issue #5629 - Fixed an issue where the user is able to edit properties when some of the collection nodes are selected.
Issue #5630 - Fixed an issue where installation of pgadmin4 not working on 32-bit Windows.
Issue #5631 - Fixed ‘cant execute empty query’ issue when remove the value of ‘USING’ or ‘WITH CHECK’ option of RLS Policy.
Issue #5633 - Ensure that create RLS Policy menu should not be visible for catalog objects.
Issue #5647 - Fixed an issue where difference DDL is showing the wrong SQL when changing the policy owner.
Issue #5662 - Fixed accessibility issue where few dialogs are not rendering properly when we zoomed in browser window 200% and screen resolution is low.
Issue #5666 - Added missing dependencies/dependent and corrected some wrongly identified.
Issue #5673 - Fixed an issue where fetching the schema throws an error if the database is not connected in Schema Diff.
Issue #5675 - Fixed CSRF errors when pgAdmin opened in an iframe on safari browser.
Issue #5677 - Fixed text color issue in explain analyze for the Dark theme.
Issue #5686 - Fixed issue where the user was not able to update policy if the policy is created with space.