pgAdmin says the utility file was not found and asks for a Binary Path
Utility file not found. Please configure the Binary Path in the Preferences dialog.Short answer
Backup, Restore and similar tools in pgAdmin run pg_dump, pg_restore and psql from a folder you choose. If that folder is unset, wrong for the server's version, or the tools are not installed, pgAdmin shows this message. Install the PostgreSQL client tools, set the Binary Path for the version in Preferences, and use Validate path.
Fix it fast
1Find out which cause you have
Find where the PostgreSQL client tools are installed. If this prints nothing, the tools are not installed and the third cause applies.
which pg_dump pg_restore psql # Windows: where pg_dump2Match what you see, then jump to its fix
- 1
The Paths > Binary paths grid is empty, or its path has no pg_dump in itThe Binary Path is not set, or points to the wrong folderFix - 2
Works for one registered server but not anotherThe path is set for a different server versionFix - 3
which pg_dump prints nothingThe PostgreSQL client tools are not installed on this computerFix
- 1
What does the error look like?
Utility file not found. Please configure the Binary Path in the Preferences dialog.
Cause 1 of 3
The Binary Path is not set, or points to the wrong folder
1Check
pgAdmin's preferences describe the PostgreSQL Binary Path as the location of the utility programs. The directory must contain pg_dump, pg_dumpall, pg_restore and psql. If you set no path, pgAdmin searches standard install locations only.
ls "$(dirname "$(which pg_dump)")"2Fix
Open Preferences, go to Paths > Binary paths, and enter the directory that holds those programs. Press Validate path; it checks that they exist and reports their versions.
# Example directory to enter in the PostgreSQL Binary Path row:
/usr/lib/postgresql/17/bin3Verify
Press Validate path, then start the backup again.
# Validate path should list pg_dump, pg_dumpall, pg_restore and psqlConfirmed by pgadmin.org
Cause 2 of 3
The path is set for a different server version
1Check
The Binary paths grid is set per PostgreSQL server version. If no path is set for a version, pgAdmin falls back to the one marked as default.
psql -h HOST -U USER -d postgres -c "SHOW server_version;"2Fix
Add a row for the server's major version, or mark the newest installed set of tools as the default, then validate the path.
# Preferences > Paths > Binary paths: set the row for the matching version3Verify
Run Validate path and check the reported version.
# Validate path shows the version of pg_dump foundConfirmed by pgadmin.org
Cause 3 of 3
The PostgreSQL client tools are not installed on this computer
1Check
pgAdmin is only the interface. On a machine with pgAdmin alone, there are no pg_dump or pg_restore programs for it to call.
pg_dump --version2Fix
Install the client package. On Ubuntu with the PostgreSQL apt repository, postgresql-client-VERSION holds the client binaries. Then set the Binary Path to where it installed them.
sudo apt update
sudo apt install postgresql-client-173Verify
Check that the tools respond.
pg_dump --version
psql --versionConfirmed by postgresql.org
How do I stop it coming back?
- Install client tools of the same major version as your newest server and keep that version as the default row.
- After upgrading PostgreSQL, revisit Binary paths: the old folder may no longer exist.
- Press Validate path whenever you change a path.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Databases
DBeaver cannot run pg_restore: the utility is not found in the client home
Utility 'pg_restore' not found in client home '/usr/lib' (/usr/lib)
DBeaver runs pg_restore from a local PostgreSQL client folder; it does not bundle one.
3 causes, each with a fixDatabases
DBeaver cannot download the PostgreSQL driver from Maven
The PostgreSQL driver files are missing and the download does not complete
DBeaver downloads the PostgreSQL JDBC driver from a Maven repository the first time you connect.
3 causes, each with a fixDatabases
python manage.py migrate finishes but the tables for my app are missing
relation "myapp_book" does not exist
migrate only applies migration files that exist.
3 causes, each with a fixDatabases
Django save fails on PostgreSQL: null value in a column violates a not-null constraint
django.db.utils.IntegrityError: null value in column "price" of relation "shop_product" violates not-null constraint
A model field is NOT NULL in the database unless it has null=True.
3 causes, each with a fixDatabases
Django migration on PostgreSQL stops with 'pending trigger events'
django.db.utils.OperationalError: cannot ALTER TABLE "mytable" because it has pending trigger events
PostgreSQL runs a Django migration in one transaction.
2 causes, each with a fixDatabases
Django cannot connect to PostgreSQL: connection refused on port 5432, locally or in Docker
Is the server running on that host and accepting TCP/IP connections?
Connection refused means nothing accepted the connection at the host and port Django used.
4 causes, each with a fix