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

Поиск
Список
Период
Сортировка
От ms@it-infrastrukturen.org
Тема BUG #6689: socket file name convention doesn't allow different IPs and the same port for different pgclusters
Дата
Msg-id E1SeW5Q-0003up-3S@wrigleys.postgresql.org
обсуждение исходный текст
Ответы Re: BUG #6689: socket file name convention doesn't allow different IPs and the same port for different pgclusters  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-bugs
The following bug has been logged on the website:

Bug reference:      6689
Logged by:          Mark
Email address:      ms@it-infrastrukturen.org
PostgreSQL version: 9.1.3
Operating system:   unbuntu-server 12.04 LTS
Description:=20=20=20=20=20=20=20=20

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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: 9.2 beta2 - pg_ctl crashes on Win32 when neither PGDATA nor -D specified
Следующее
От: sergey-1987@yandex.ru
Дата:
Сообщение: BUG #6690: ALL and ANY array operators