Should I edit User PATH or System PATH?

For a single user, editing the User PATH is sufficient. Use System PATH if you want all users and services to see psql.

Do I need to reboot after editing PATH?

No full reboot is required, but you must close and reopen terminals and apps to load the updated PATH.

Keep only one bin folder in PATH or ensure the desired version appears first to avoid version conflicts.

Both work. Ensure the updated PATH is visible in the shell session you opened after the change.

Press Win + R, type sysdm.cpl, press Enter.
Go to Advanced → click Environment Variables….
Under User variables, select Path → Edit….
Click New and paste your PostgreSQL bin path, e.g., C:\\Program Files\\PostgreSQL\\18\\bin.
Use the arrows to move it above any older PostgreSQL entries.
Click OK on all dialogs to apply. Close and reopen your terminal/app.

Run Command Prompt as your user (or as Administrator if you want to edit the System PATH). Replace the path with your version.

Append to User PATH:
setx PATH "%PATH%;C:\\Program Files\\PostgreSQL\\18\\bin"
Append to System PATH (requires elevated CMD):
setx /M PATH "%PATH%;C:\\Program Files\\PostgreSQL\\18\\bin"
Close and reopen the terminal, then verify:
where psql and psql --version

Use PowerShell to add to the User PATH. Reopen apps after applying.

Show current User PATH:
[Environment]::GetEnvironmentVariable("Path", "User")
Add PostgreSQL bin:
$p = [Environment]::GetEnvironmentVariable("Path","User"); if (-not $p.EndsWith(";")) { $p += ";" }; $p += "C:\\Program Files\\PostgreSQL\\18\\bin"; [Environment]::SetEnvironmentVariable("Path", $p, "User")
Reopen PowerShell/CMD, then verify with where psql.

Close and reopen the terminal/app. Ensure the bin path is correct and appears before older PostgreSQL paths.

Keep only one PostgreSQL bin in PATH, or place the desired version first. Verify with where psql.

Editing System PATH requires elevation. If you only changed User PATH, services won’t see it. Use System PATH for service contexts.