Lock file conflict with multiple postmasters

From: Nicola Mauri <Nicola(dot)Mauri(at)saga(dot)it>
To: pgsql-admin(at)postgresql(dot)org
Subject: Lock file conflict with multiple postmasters
Date: 2007-04-17 16:26:16
Message-ID: OF895957EA.B63077EE-ONC12572C0.0057B976-C12572C0.005A5119@saga.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi,
We have two postmasters on the same host. They are configured to listen on
port 5432 of two distinct IP addresses as follows:

/var/lib/pgsql1/data/postgresql.conf:
listen_addresses = '10.0.0.1'
port = 5432
/var/lib/pgsql2/data/postgresql.conf
listen_addresses = '10.0.0.2'
port = 5432

However, if we start the second instance while the first one is running,
we get the following error:
FATAL: could not open lock file "/tmp/.s.PGSQL.5432.lock": Permission
denied

So, lock filename cares only about port number and nothing else.
In order to avoid this conflict, how can we configure the name of
lockfiles or directory where they are placed?

Thanks in advance!
Nicola

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Chuck Amadi 2007-04-17 16:50:36 Is there any good helpful howtos and gotchas
Previous Message Hajek, Nick 2007-04-17 15:27:42 Re: Is anyone running version 8.2.3 on SuSE 10.2