Postgres.app

Troubleshooting & Support

Warnings

Reindexing required / Reindexing recommended

See this dedicated page.

Common errors

The following list contains all errors which may occur while you’re using Postgres.app.

PostgreSQL version not installed

Postgres.app includes the PostgreSQL binaries inside the application package. Each version is available bundled with either a single or all currently supported versions of PostgreSQL.

This error means that the binaries for this server are not included in the installed bundle. If the required version is still supported, you can download a different bundle from this page. If the version is no longer supported, you can find the last release supporting that version under legacy downloads. Please note that these releases are no longer maintained and you should migrate your data to a new version as soon as possible.

After the first start of Postgres.app, it is possible to alter the available versions of PostgreSQL by copying the wanted versions out of the application package of other releases to the directory /Applications/Postgres.app/Contents/Versions/.

Port [number] is already in use

This error usually means that you already have a PostgreSQL server running on your Mac. If that is running within Postgres.app, expand the sidebar and stop that other server or alter the ‘Port’ under the button ‘Database Settings’.

If there isn’t an other server running within Postgres.app, you likely have a different installation of PostgreSQL running on your machine. To uninstall this, see the instructions on this page

It can also happen when a different user on your Mac is already running Postgres.app. Only a single server can run on each port.

If you want to use multiple PostgreSQL servers simultaneously, configure them to use a different port.

There is already a PostgreSQL server running in this data directory

This can happen if you’ve configured Postgres.app to use a data directory that is used by a different PostgreSQL installation. Stop the other server before starting Postgres.app. In general, it is not recommended to just use a data directory created by another version of PostgreSQL, since it might have been configured differently.

Could not delete stale postmaster.pid file

To keep track of the PostgreSQL server process, PostgreSQL stores the process id for the server in a file named postmaster.pid in the server’s data directory. If PostgreSQL crashes, this file can contain an old pid that prevents PostgreSQL from starting.

Postgres.app detects this problem and tries to automatically delete this stale postmaster.pid file if necessary.

If you see the error message “Could not delete stale postmaster.pid file”, then Postgres.app for some reason failed to delete this file.

You may be able to fix the problem by deleting the file manually.

The data directory contains an old postmaster.pid file / The data directory contains an unreadable postmaster.pid file

Previous versions of Postgres.app showed this error when the data directory contains a stale postmaster.pid file.

To fix this problem, you can either upgrade to the latest version of Postgres.app; or you can manually delete the file postmaster.pid in the data directory.

Could not initialize database cluster

This error means that the initdb command failed. This should not happen. If it does, please open an issue on Github. For troubleshooting, try executing the following command manually:

/Applications/Postgres.app/Contents/Versions/latest/bin/initdb -D "DATA DIRECTORY" -U postgres --encoding=UTF-8 --locale=en_US.UTF-8

Could not create default user / Could not create user database

After the data directory is initialized, Postgres.app creates a default user and database. This error means that creating the user has failed. Check the server log (inside the data directory) for details.

You can try creating a default user and database manually:

/Applications/Postgres.app/Contents/Versions/latest/bin/createuser -U postgres -p PORT --superuser USERNAME
/Applications/Postgres.app/Contents/Versions/latest/bin/createdb -U USERNAME -p PORT DATABASENAME

Postgres.app uses your system user name for USERNAME and DATABASENAME by default.

File [or Folder] not found. It will be created the first time you start the server

Data directories and all its contents are only created when you start a server the first time. This error occurs when you attempt to open a data directory (or file) which doesn’t exist yet. Start the server first and try again.

Unknown Error

This error should not occur. Please open an issue on Github and provide a detailed description what lead to this error.

Errors in the server log

The server log is inside the data directory in a file named postgres-server.log.

Here are some errors that could appear:

Could not create listen socket for “localhost”

Usually this error is caused by broken /etc/hosts file. The problem could be a missing localhost entry, syntax errors or incorrect whitespace.

For reference, here is what this file should look like by default on macOS:

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1	localhost
255.255.255.255	broadcasthost
::1             localhost 

database files are incompatible with server: The database cluster was initialized with PG_CONTROL_VERSION x, but the server was compiled with PG_CONTROL_VERSION y

This error usually happens when you try to start a server that was initialized with a prerelease version of PostgreSQL. The on disk data format sometimes changes between pre-release versions. You need to start the server with the version you initialized it with, then dump the database, then create a new server with the new version and restore.

Errors when connecting to the PostgreSQL server

psql: FATAL: role “USERNAME” does not exist

By default, Postgres.app creates a PostgreSQL user with the same user as your system user name. When this error occurs, it means that this user does not exist. You can create it by executing the following command in the Terminal:

1. Make sure your $PATH is configured correctly
2. Execute the command createuser -U postgres -s $USER

• -U postgres tells createuser to connect with the postgres user name
• -s tells createuser to create a super user
• $USER is a variable containing your system user name, and tells createuser the name of the postgres user you want to create

psql: FATAL: database “USERNAME” does not exist

By default, psql tries to connect to a database with the same name as your local user. This error means that this database does not exist. This can have several possible reasons:

• Postgres.app failed to create the default database when initializing the server
• You deleted the default database
• Your user name is different from the user name that initialized the server

There are multiple ways to fix this problem:

1. Make sure your $PATH is configured correctly
2. You can create the missing database using the command createdb $USER, or
3. You can connect to a different database, eg. psql postgres to connect to the other default database

Could not translate host name “localhost”, service “5432” to address: nodename nor servname provided, or not known

Usually this error is caused by broken /etc/hosts file. The problem could be a missing localhost entry, syntax errors or incorrect whitespace.

For reference, here is what this file should look like by default on macOS:

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1	localhost
255.255.255.255	broadcasthost
::1             localhost 

psql: FATAL: could not open relation mapping file “global/pg_filenode.map”: No such file or directory

This error can occur when you delete the data directory while the PostgreSQL server is still running. To fix it, kill all PostgreSQL processes or restart your computer. Then start a new PostgreSQL server.

Postgres.app failed to verify “trust” authentication

See this dedicated page.

Postgres.app rejected “trust” authentication

See this dedicated page

Starting the server manually

For debugging, it is often useful to try starting the server manually:

1. Quit Postgres.app
2. Open the Terminal and type /Applications/Postgres.app/Contents/Versions/latest/bin/postgres -D "DATA DIRECTORY" -p PORT (replace DATA DIRECTORY with your data directory, make sure to include the quotes because the path might contain spaces)
3. Now you should see a more detailed error message why the server failed to start

Resetting Postgres.app

If you somehow mess up your Postgres.app installation, here’s how to start fresh.
CAUTION: This will delete all your databases, tables and data!

1. Quit Postgres.app using the menu item
2. Open Activity Monitor, see if any processes name postgres are running. If so, kill them. Kill the process with the lowest pid first; child processes are respawned automatically after killing them.
3. Delete the Folder ~/Library/Application Support/Postgres
4. Delete all settings using the command: defaults delete com.postgresapp.Postgres2
5. Open Postgres.app again

Technical Support

If you run into any issues using Postgres.app, your first stop should be the issue tracker on Github.

Help others

If you encounter an issue and find a way to fix it, consider contributing to this documentation. This page is hosted on Github.