---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
I'm trying to impliment an automatic failover system, and am running into
the problem that when I try to start multiple postgres clusters on the
same box, postgres will not start if /tmp/.s.PGSQL.5432.lock exists. Can I
change the file it's looking for via an option? Nothing seemed obvious
from a quick review of the docs, short of (presumably) changing the port
number, which I don't want to do.
- [GENERAL] changing the /tmp/ lock file? Ben
- Re: [GENERAL] changing the /tmp/ lock file? Tom Lane
- Re: [GENERAL] changing the /tmp/ lock file... Ben
- Re: [GENERAL] changing the /tmp/ lock ... Greg Smith
- Re: [GENERAL] changing the /tmp/ lock ... Tom Lane
- Re: [GENERAL] changing the /tmp/ lock ... Robin Ericsson
- Re: [GENERAL] changing the /tmp/ l... Ben
- Re: [GENERAL] changing the /t... Martijn van Oosterhout
- Re: [GENERAL] changing the /tmp/ lock file? Greg Smith