pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedLock file conflict with multiple postmasters
2+ messages / 2 participants
[nested] [flat]
* Lock file conflict with multiple postmasters
@ 2007-04-17 16:26 Nicola Mauri <Nicola.Mauri@saga.it>
0 siblings, 1 reply; 2+ messages in thread
From: Nicola Mauri @ 2007-04-17 16:26 UTC (permalink / raw)
To: 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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Lock file conflict with multiple postmasters
@ 2007-04-17 17:23 Tom Lane <tgl@sss.pgh.pa.us>
parent: Nicola Mauri <Nicola.Mauri@saga.it>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2007-04-17 17:23 UTC (permalink / raw)
To: Nicola Mauri <Nicola.Mauri@saga.it>; +Cc: pgsql-admin
Nicola Mauri <Nicola.Mauri@saga.it> writes:
> In order to avoid this conflict, how can we configure the name of
> lockfiles or directory where they are placed?
unix_socket_directory
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2007-04-17 17:23 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-04-17 16:26 Lock file conflict with multiple postmasters Nicola Mauri <Nicola.Mauri@saga.it>
2007-04-17 17:23 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox