Re: Pre-version pg_upgrade syntax check

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Pre-version pg_upgrade syntax check
Date: 2020-02-10 22:59:24
Message-ID: 03ebdc12-d8f6-8310-9552-f7a744fe3e73@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/10/20 1:59 PM, Rich Shepard wrote:
> Running Slackware-14.2/x86_64. Current installation is postgres-11.5 and
> I'm
> upgrading to postgresql-12.1. Both versions are installed and stopped.
>
> If I have correctly read the pg_upgrade manual page this is the command to
> use (as user postgres) with lines split to fit the message; the command
> will
> be on a single line:
>
> pg_upgrade \
> -b /usr/lib64/postgresql/11/bin/ \
> -B /usr/lib64/postgesql/12/bin/ \
> -d /var/lib/pgsql/11/data/ \
> -D /var/lib/pgsql/12/data/ \
> -p 5432 \
> -P 5432
>
> I don't know that the port numbers are required.

They are not:

https://www.postgresql.org/docs/12/pgupgrade.html

"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. You can use the same port number for both clusters
when doing an upgrade because the old and new clusters will not be
running at the same time. However, when checking an old running server,
the old and new port numbers must be different."

>
> Have I missed an option?

Not a required one. Best way to find out is to run --check.

>
> Rich
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rich Shepard 2020-02-10 23:30:51 Re: Pre-version pg_upgrade syntax check
Previous Message Rich Shepard 2020-02-10 22:00:43 Re: Pre-version pg_upgrade syntax check