listen_addresses

listen_addresses is the PostgreSQL setting that defines the host name or IP address(es) to listen to.

Note

Fact — official short description: “Sets the host name or IP address(es) to listen to.”

Identity

Type , Valuestring: Upstream pg_settings type
Context , Valuepostmaster: Requires a server restart
Unit , Value—: Raw unit
Range , Value—: Raw limits in the last observed version
Enum values , Value—: — for non-enum types
Category , ValueConnections and Authentication / Connection Settings: Upstream classification
Latest boot value , Valuelocalhost: localhost

Lifecycle

Fact	Value
First observed	PG9.0 (research boundary)
Present in	PG9.0–19 Beta 3
Removed in	No
Introduction commit	Not asserted: predates the PG9.0 research boundary
Commit date	—
Discussion	—

Default history

Measured PG9.0–19 Beta 3 boot defaults
Versions	Raw `boot_val`	Unit	Human value
PG9.0–19 Beta 3	`localhost`	—	localhost

How it works

listen_addresses sets the host name or IP address(es) to listen to. The server binds the listed interfaces at startup; reachability still depends on port, pg_hba.conf, host firewalls, and network routing.

listen_addresses is a POSTMASTER-context setting: PostgreSQL reads it during server startup, and a configuration reload or session SET cannot activate a new value.

The listener endpoint combines listen_addresses and port at startup, while pg_hba.conf, TLS, firewalls, routing, and service discovery determine which clients can use it.

Tuning advice

Tip

Advice. These are workload-specific starting points and must be validated with measurements.

Workload	Guidance
OLTP	Set listen_addresses from the service topology and expose only required interfaces or ports. Validate poolers, health checks, pg_hba.conf, firewalls, failover, and restart sequencing together.
OLAP	Use an explicit analytical endpoint or network when isolation is required, but keep connection information consistent across failover targets.
Small nodes	Prefer local-only exposure unless remote access is required. Preserve a tested administrative route before changing listen_addresses and restarting.

Pigsty

Values use the fixed 8-vCPU, 32-GiB, 100-GiB SSD fixture and render the current Pigsty templates for PG19 Beta 3; this does not assert current Pigsty support for that historical or beta release.

Template	Effective value	Versus upstream boot	Source expression
OLTP	Unmodified	—	—
OLAP	Unmodified	—	—
CRIT	Unmodified	—	—
TINY	Unmodified	—	—

Caution

Advice — pending human review. Fact from the current Pigsty template projection: OLTP: PG9.0–19 Beta 3 unmodified; OLAP: PG9.0–19 Beta 3 unmodified; CRIT: PG9.0–19 Beta 3 unmodified; TINY: PG9.0–19 Beta 3 unmodified. No Pigsty-specific rationale is inferred from an absent override.

Common pitfalls

Expecting a reload or SET to activate listen_addresses, although it requires a controlled server restart.
Assuming a bound address or port grants access; pg_hba.conf and operating-system or network controls still apply.
Changing a startup-only endpoint without updating discovery, health checks, firewalls, clients, and the administrative recovery path.
Changing listen_addresses globally without a rollback plan and a client or operational compatibility test.

port · max_connections · reserved_connections · superuser_reserved_connections · unix_socket_directories