From: Ziggy Skalski <zskalski@afilias.info>
To: pgsql-admin@postgresql.org
Subject: Re: Postgres update 9.1 to 9.3 - error port 50432
Date: Fri, 30 Jan 2015 14:48:26 -0500
Message-ID: <54CBE00A.7050405@afilias.info> (raw)
In-Reply-To: <1422646122654-5836200.post@n5.nabble.com>
References: <CAOQWw8ShKQEK=18wMjBL4Bt4V4d_N-GVjXzorBxw_XM_Yt15sw@mail.gmail.com>
<54CBD5EF.3010704@afilias.info>
<1422646122654-5836200.post@n5.nabble.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: zskalski@afilias.info
Subject: Re: Postgres update 9.1 to 9.3 - error port 50432
In-Reply-To: <54CBE00A.7050405@afilias.info>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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