Hey there, let's fix this psql issue you're hitting after setting up PostgreSQL via EnterpriseDB on macOS. I've walked plenty of developers through this exact scenario, so let's break down the most common fixes step by step:

1. 先检查PostgreSQL的bin目录是否在系统PATH中 #

This is the #1 culprit 9 times out of 10—macOS doesn't automatically add EnterpriseDB's PostgreSQL path to your system's PATH.

• First, find your install path: EnterpriseDB typically puts PostgreSQL at /Library/PostgreSQL/<你的版本号>/bin (e.g., /Library/PostgreSQL/16/bin).
• Open your terminal and run echo $PATH to see if this directory shows up in the output.
• If it's missing, add it to your shell config:
  • For Zsh (macOS's default shell now), edit ~/.zshrc and add this line:

    export PATH="/Library/PostgreSQL/<你的版本号>/bin:$PATH"
    

  • For Bash, edit ~/.bash_profile or ~/.bashrc with the same line.
  • Save the file and run source ~/.zshrc (or your corresponding config file) to apply the change immediately.
  • Verify it worked with echo $PATH, then try running psql again.

2. 确认PostgreSQL服务正在运行 #

Sometimes the server doesn't start automatically after installation, which will block psql from connecting.

• Open System Preferences, look for the PostgreSQL icon (added by EnterpriseDB), and check if the service status says "Running".
• If it's stopped, click "Start Server" to fire it up.
• Alternatively, use the terminal to start it (replace with your version number):

  sudo /Library/PostgreSQL/<版本号>/bin/pg_ctl -D /Library/PostgreSQL/<版本号>/data start
  

3. 验证你调用的是正确的psql版本 #

If you had an older PostgreSQL installation before, your system might be trying to run that outdated psql instead of the one you just installed.

• Run which psql in the terminal. The output should point to the EnterpriseDB bin directory you checked earlier.
• If it's pointing somewhere else, test with the full path first:

  /Library/PostgreSQL/<版本号>/bin/psql -U postgres
  

  (The default superuser is postgres—enter the password you set during installation when prompted.)

4. 可选：设置默认连接环境变量 #

If you still get connection errors, setting these variables can simplify testing the local connection:

export PGUSER=postgres
export PGDATABASE=postgres

Then run psql again—it'll automatically use the postgres user to connect to the default postgres database.

If none of these steps work, share the exact error message you're seeing (like "command not found" or "could not connect to server") and we can dig deeper!

内容的提问来源于stack exchange，提问作者Ronit Mankad