Problem starting PG-9.2 on non-default port

From: "James B(dot) Byrne" <byrnejb(at)harte-lyne(dot)ca>
To: pgsql-general(at)postgresql(dot)org
Subject: Problem starting PG-9.2 on non-default port
Date: 2012-12-14 14:26:46
Message-ID: 87eae6ad8b3176226aeed30bef6a2de5.squirrel@webmail.harte-lyne.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I wish to run an instance of PG-9.2 concurrently with our production
version (9.1). I have changed the listening port number.

listen_addresses = 'pgsql-dbms.hamilton.harte-lyne.ca, localhost'
#port = 5432 # (change requires restart)
port = 5433

However, I am getting this error when I try to start the new version
while the old one is still running. Is there something else I must do
to accomplish this? Why is the lock file using the default port
number for this instance?

cat ../pgstartup.log
2012-12-14 09:13:41 EST : LOG: XX000: could not bind IPv4 socket:
Address already in use
2012-12-14 09:13:41 EST : HINT: Is another postmaster already
running on port 5432? If not, wait a few seconds and retry.
2012-12-14 09:13:41 EST : LOCATION: StreamServerPort, pqcomm.c:438
2012-12-14 09:13:41 EST : WARNING: 01000: could not create listen
socket for "pgsql-dbms.hamilton.harte-lyne.ca"
2012-12-14 09:13:41 EST : LOCATION: PostmasterMain, postmaster.c:892
2012-12-14 09:13:41 EST : FATAL: F0001: lock file
"/tmp/.s.PGSQL.5432.lock" already exists
2012-12-14 09:13:41 EST : HINT: Is another postmaster (PID 1299)
using socket file "/tmp/.s.PGSQL.5432"?
2012-12-14 09:13:41 EST : LOCATION: CreateLockFile, miscinit.c:822

--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB(at)Harte-Lyne(dot)ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2012-12-14 14:28:09 Re: initdb error
Previous Message Merlin Moncure 2012-12-14 14:21:44 Re: XML Schema for PostgreSQL database