BUG #6689: socket file name convention doesn't allow different IPs and the same port for different pgclusters

From: ms(at)it-infrastrukturen(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #6689: socket file name convention doesn't allow different IPs and the same port for different pgclusters
Date: 2012-06-12 18:45:04
Message-ID: E1SeW5Q-0003up-3S@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 6689
Logged by: Mark
Email address: ms(at)it-infrastrukturen(dot)org
PostgreSQL version: 9.1.3
Operating system: unbuntu-server 12.04 LTS
Description:

When using /var/run/postgresql/ as unix_socket_directory for "main" and
"second" pgcluster and different IP-interfaces (addresse) for every
pgcluster (but the same default port number), there are different pid file
names (like 9.1-main.pid and 9.1-secondpg.pid) *but* names of unix_sockek
files doesn't follow such name conventions.

It results in error when trying to run the second pgcluster with another IP
but the same (default port 5432):
Error: Port conflict: another instance is already running on on
/var/run/postgresql with port 5432

regards, Mark

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Josh Kupershmidt 2012-06-12 20:27:14 Re: Tab completion of function arguments not working in all cases
Previous Message Amit Kapila 2012-06-12 12:54:15 Re: 9.2 beta2 - pg_ctl crashes on Win32 when neither PGDATA nor -D specified