Port5432— PostgreSQL
PostgreSQL defaults to TCP 5432 and also supports local Unix sockets. Databases within one instance share that instance’s listening port.
Registry assignments, software defaults and local listeners are different things. A port number alone does not identify or secure a service.
Configuration and troubleshooting
Inspect port and listen_addresses in postgresql.conf, then source and authentication rules in pg_hba.conf. Plan a restart window for listener-setting changes.
Important limitations
Connection refusal, timeout and authentication failure require different checks. Do not broaden pg_hba.conf to trust as a shortcut around permissions.
Read-only checks: run on the server host
Choose the commands for your OS. Check TCP and UDP separately. No result is not a lasting availability guarantee; inspect host and container separately.
Linux
sudo ss -ltnp 'sport = :5432'macOS
sudo lsof -nP -iTCP:5432 -sTCP:LISTENWindows PowerShell
Get-NetTCPConnection -LocalPort 5432 -State ListenSources and review
Sources checked on:
This review covers the explanations and sources on this page, not your device or every community software entry below.
Software Using This Port (1 software)
Community software entries: links are references, not individual verification.
Usage Suggestions
- Before using port 5432, please confirm it is not occupied by other services
- If you encounter port conflicts, consider using other ports or stopping the occupying service
Frequently asked questions
What is port 5432 used for?
Port 5432 sits in the Database category. This page lists the registered purpose and the software commonly associated with it; to see what is actually listening on a specific machine, check the process with ss/netstat.
Is port 5432 TCP or UDP?
The registered protocol on this page is TCP. The same number behaves independently on each protocol: TCP may be listening while UDP is idle, so check them separately.
How do I check if port 5432 is in use?
On Linux: sudo ss -tlnp 'sport = :5432' for an exact port match. On macOS: sudo lsof -nP -iTCP:5432 -sTCP:LISTEN. On Windows PowerShell: Get-NetTCPConnection -LocalPort 5432 -State Listen. A listener counts as confirmed only when you can see the bind address and process name; without root/admin you will not see other users' processes.
Is port 5432 secure? Should I open it in my firewall?
A port number has no inherent security — it depends on whether the listening service is correctly configured and whether it needs exposure at all. Keep loopback/internal-only services firewalled; where public access is required, pair it with source restrictions, VPN or authentication. The caution section on this page lists port-specific risks.
Quick Info
- Port
- 5432
- Protocol
- TCP
- Categories
- Database
- Usage Status
- 1 software in use
Related Ports
Need Help?
If you find incorrect information or need to add more, please submit correction information.
Submit Correction