Skip to main content

Step-by-Step Guide to Changing the PostgreSQL Listening Port on Windows

Updated by Tim Rabbetts on
Changing PostgreSQL Listening Port on Windows

Changing the listening port for PostgreSQL on Windows can be crucial for resolving conflicts with other applications or for security configurations. Here’s a step-by-step guide on how to change the PostgreSQL listening port on a Windows system.

Step 1: Locate the Configuration File

First, you need to locate the postgresql.conf file. This file is typically found in your PostgreSQL installation's data directory. The default path usually is C:\Program Files\PostgreSQL\\data, where is the version number of PostgreSQL you are using.

Step 2: Open the Configuration File

Open the postgresql.conf file using a text editor with administrative privileges. You can use editors like Notepad or Notepad++.

Step 3: Change the Listening Port

Find the line that starts with #port = 5432 where 5432 is the default port used by PostgreSQL. Change the port number to your desired port and remove the '#' at the beginning of the line to enable the setting. For instance:

port = 5433

Step 4: Save and Close the File

After changing the port number, save the changes and close the editor.

Step 5: Restart PostgreSQL Service

For the changes to take effect, you need to restart the PostgreSQL service. You can do this through the Services app in Windows:

  1. Press Windows + R, type services.msc, and press Enter.
  2. Scroll down to find PostgreSQL service.
  3. Right-click the service and choose Restart.

Alternatively, you can restart the service using the command line:

net stop postgresql && net start postgresql

Verifying the Change

To verify that PostgreSQL is now listening on the new port, you can use the psql utility:

psql -h localhost -p new_port

Replace new_port with the port number you have set.

Conclusion

Changing the listening port for PostgreSQL on a Windows system is a straightforward process that can be achieved by editing the configuration file and restarting the service. This is often necessary for troubleshooting, performance tuning, or enhancing the security of your database server.