Re: Postgres update 9.1 to 9.3 - error port 50432

From: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Postgres update 9.1 to 9.3 - error port 50432
Date: 2015-01-30 19:28:42
Message-ID: 1422646122654-5836200.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Ziggy Skalski wrote
>> connection to database failed: could not connect to server: No such
>> file or directory
>> Is the server running locally and accepting
>> connections on Unix domain socket "/var/lib/pgsql/.s.PGSQL.50432"?
> Is there a backend running on port 50432 or is this a typo and it was
> supposed to be 5432 in the above pg_upgrade command?

Ziggy:

I suggest you read the pg_upgrade documentation.

http://www.postgresql.org/docs/9.4/static/pgupgrade.html

Specifically the part where it says:

"Obviously, no one should be accessing the clusters during the upgrade.
pg_upgrade defaults to running servers on port 50432 to avoid unintended
client connections."

David J.

--
View this message in context: http://postgresql.nabble.com/Postgres-update-9-1-to-9-3-error-port-50432-tp5836178p5836200.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message MauricioLeite 2015-01-30 19:34:08 Re: Postgres update 9.1 to 9.3 - error port 50432
Previous Message Payal Singh 2015-01-30 19:10:27 Re: Postgres update 9.1 to 9.3 - error port 50432