Re: Postgres update 9.1 to 9.3 - error port 50432 - Mailing list pgsql-admin

From Ziggy Skalski
Subject Re: Postgres update 9.1 to 9.3 - error port 50432
Date
Msg-id 54CBE00A.7050405@afilias.info
Whole thread Raw
In response to Re: Postgres update 9.1 to 9.3 - error port 50432  (David G Johnston <david.g.johnston@gmail.com>)
List pgsql-admin
On 15-01-30 02:28 PM, David G Johnston wrote:
> 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.
>
>
>

Ah ok, I usually specify the ports when running pg_upgrade so didn't run
into that error message before :)

Z


pgsql-admin by date:

Previous
From: MauricioLeite
Date:
Subject: Re: Postgres update 9.1 to 9.3 - error port 50432
Next
From: John Scalia
Date:
Subject: Re: Postgres update 9.1 to 9.3 - error port 50432