Latest Videos

Want to see your pgAdmin video here? Email webmaster@pgadmin.org.

All videos

Latest Blog Posts

How to setup Two Factor Authentication in pgAdmin 4

Author: Akshay Joshi, date: Dec. 7, 2022

Two-Factor Authentication (2FA) works by adding an additional layer of security to your online accounts. It requires an additional login credential - something you have - to gain account access, in addition to your password (something you know).

This feature is only available in Server Mode.

pgAdmin 4 supports two types of 2FA:

• Email Authentication
• Authenticator App (e.g: Google Authenticator)

Read more

Psycopg2 to Psycopg3 migration in pgAdmin 4

Author: Khushboo Vashi, date: Dec. 7, 2022

Recently the Psycopg project released a major version, Psycopg3. pgAdmin 4 is immensely dependent on psycopg2 as it is being used as a database driver and the pgAdmin team decided to migrate to the new latest version.

Initially, we thought that it would be hardly 3 to 4 weeks work as it is just a migration but our assumption was incorrect. The reason is we haven’t used psycopg2 "out of the box", we have extended many things and one of them is cursor factory. So, when I started porting, I realized the way we have done that is not supported any more, so I have started digging into the code and found out that in the next release, that was supposed to be included. So, I cloned the repo, built it on my local and used it till 3.1 official release.

Psycopg3 is completely rewritten, so it’s a vast topic to cover, but we will look at some of the areas which affected pgAdmin.

Read more

How to use an external database for pgAdmin user settings

Author: Akshay Joshi, date: Nov. 18, 2022

The purpose of this blog is to illustrate how to save pgAdmin 4 configurations to an external database server. In addition, we covered examples that demonstrate how to use PostgreSQL server as an external database.

Read more

News

2023-03-09 - pgAdmin 4 v6.21 Released

The pgAdmin Development Team is pleased to announce pgAdmin 4 version 6.21. This release of pgAdmin 4 includes 19 bug fixes and new features. For more details please see the release notes.

Note:

This is the last release of pgAdmin that will support Python 3.6 and Psycopg2. Future releases will require Python 3.7 or later. This means that this is also the last release that will be supported on CentOS and RHEL 7.x

Notable changes in this release include:

Features:

• Allow changing cardinality notation in ERD to use Chen notation.
• Add additional logging for successful logins and user creation.

Bugs/Housekeeping:

• Fixed an issue where pgAdmin failed to connect when the Postgres password included special characters.
• Ensure that the database migration does not fail with a NoSuchTableError exception.
• Fixed an issue where the database server is not connected using a service file.
• Handle MERGE operation in query tool explain introduced in PostgreSQL 15.
• Ensure that the schema diff tool should pick up the change in the column grants.
• Ensure that Grant column permission to a view is visible in the SQL tab.
• Ensure that content on the DDL comparison panel should get refreshed on selecting the object using the up and down arrow keys.
• Fixed an issue where the user can't create trigger AFTER UPDATE OF.
• Do not allow to save invalid JSON in query tool JSON editor.

Download your copy now!

2023-02-09 - 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.

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.

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:

Features:

• 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.

Bugs/Housekeeping:

• Use uplot for Dashboard graphs to reduce CPU usage.
• Fixed an issue where the client cert location was not stored on the shared servers.
• Fix orphan database connections resulting in an inability to connect to databases.
• Ensure that the system columns should not visible in the import/export data.
• Increase the length of the value column of the setting table.
• Fix an issue where drag and drop object names are not working.
• Fix an issue where the role is used as a username for newly added servers when opening the query tool.
• Fixed an issue where Query history is not getting loaded with the external database.
• Fix failing import servers CLI due to vulnerability fix

Download your copy now!

2023-01-17 - pgAdmin 4 v6.19 Released

The pgAdmin Development Team is pleased to announce pgAdmin 4 version 6.19. This release of pgAdmin 4 includes 20 bug fixes and new features. For more details please see the release notes.

Notable changes in this release include:

Features:

• Added support of AWS provider for BigAnimal cloud deployment.

Bugs/Housekeeping:

• Ensure that the authenticated users can't access each other's directories and files by providing relative paths. (CVE-2023-0241).
• Allow YouTube video demo links to be added to appropriate pgAdmin documentation.
• Fixed an issue where an incorrect password was used with the shared server.
• Ensure the browser tree does not freeze while rendering 10k+ nodes/objects.
• Fixed an issue where the default value of string for columns should wrap in quotes in the create script.
• Fix the webserver and internal authentication setup issue.
• Ensure the appbundle has correct permissions so that pgAdmin can be accessed by users other than the owner.
• Fixed a missing "jwks_uri" in metadata error that occurred when logging in with an oAuth2 provider like Azure or Google.
• Fixed an issue where the Geometry viewer does not show the popup when columns are less than 3.

Download your copy now!

2022-12-20 - pgAdmin 4 v6.18 Released

The pgAdmin Development Team is pleased to announce pgAdmin 4 version 6.18. This release of pgAdmin 4 includes 13 bug fixes and new features. For more details please see the release notes.

Notable changes in this release include:

Features:

• Added native menu support in desktop mode.

This feature converts the top-level menu to a native menu using NWjs. As a result, it uses the look and feel of the platform that it runs on when in Desktop mode.

• Enhancements to the ERD when selecting a relationship.

Bugs/Housekeeping:

• Fixed an issue where Transaction IDs were not found in session in the Query Tool.
• Fixed an issue where tablespace was missing on partition tables in SQL.
• Fixed an issue where properties tab was refreshing on tab change even if the selected node is same.
• Fixed an issue with auto-complete not working as expected with double quotes.
• Ensure that table statistics are sorted by size.
• Fixed an issue while updating server node info removes the clear saved password menu.
• Fixed an issue where master password was not set correctly with external config database.
• Fixed an error in the collation create script for PG-15.
• Fixed BigAnimal authentication aborted issue.

Download your copy now!

2022-12-02 - pgAdmin 4 v6.17 Released

The pgAdmin Development Team is pleased to announce pgAdmin 4 version 6.17. This release of pgAdmin 4 includes 10 bug fixes and new features. For more details please see the release notes.

Security Release

Please note that this release includes a security update to ensure only authorized and authenticated users can validate binary paths when using pgAdmin running in server mode. Users running pgAdmin in server mode should upgrade to this release as soon as possible.

This issue does not affect users running in desktop mode.

Notable changes in this release include:

Bugs/Housekeeping:

• Ensure that only authorized and authenticated users can validate binary paths (CVE-2022-4223).
• Update the BigAnimal API version to V2.
• Remove all traces of Backbone and Underscore.
• Fixed an issue where the wrong schema is displayed for a foreign key in the schema diff tool.
• Ensure that the query history date format in Desktop mode matches the format of the locale of the pgadmin server.
• Fixed an issue where the CSV file would not download if the CSV quote character length exceeded 1.
• Ensure that DATA_DIR dependent folders/files are automatically created inside the specified DATA_DIR if they are not specified separately in the configuration file.
• Fixed an issue where the editor position was wrong when editing data from the result grid.
• Ensure the query tool is launched successfully for the servers registered with the PostgreSQL service.

Download your copy now!

2022-09-21 - Project moved to GitHub

The pgAdmin Project has now moved to GitHub!

The source code repository can be found at: https://github.com/pgadmin-org/pgadmin4.

Issues can be found at https://github.com/pgadmin-org/pgadmin4/issues. All issues have been migrated from the old Redmine trackers.

There are a number of other repositories also in our GitHub organisation for pgAgent, the website, and old versions of pgAdmin.

Please update your links and bookmarks accordingly!

2022-07-11 - pgAdmin User Survey

In order to help us better plan the future of pgAdmin, it's essential that we hear from users so we can focus our efforts in the areas that matter most.

We'd like to gather feedback from as many users as possible, so please take a few minutes and complete the survey below. Feel free to share the link with any friends or colleagues who you think may also want to provide their input.

https://forms.gle/62gzUPNbj4N1jNTB6

Please note that the survey is entirely anonymous (although Google will see your IP address, and may know who you are if you are logged in to your Google account), unless you choose to include any identifying information in any of your responses.

Thank you!

2018-07-12 - pgAgent v4.0.0 Released

The pgAdmin Development Team are pleased to announce the release of pgAgent v4.0.0.

pgAgent is a job scheduler for PostgreSQL; for more information please see the documentation included as part of the pgAdmin documentation at https://www.pgadmin.org/docs/pgadmin4/3.x/pgagent.html.

Download (source): https://www.pgadmin.org/download/pgagent-source-code/

We expect DEB and RPM packages to be available from the PostgreSQL APT/YUM repositories in due course, as well as an updated installer from EnterpriseDB available through StackBuilder.

Notable changes in this release include:

• Remove the dependency on wxWidgets. pgAgent now uses Boost for thread management and synchronisation [Neel Patel]
• Refactor connection parsing logic to fix issues with and improve handling of connection strings [Thomas Krennwallner]
• Handle 2 digit server version numbers [Ashesh Vashi]
• Fix handling of the "succeeded" flag on job steps which could prevent failure of steps causing the following steps to fail [Sanket Mehta]

Postgres, PostgreSQL and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada, and used with their permission.